-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbitrise.yml
124 lines (112 loc) · 3.9 KB
/
bitrise.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
format_version: 1.4.0
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
# define these in your .bitrise.secrets.yml
- BITRISE_BUILD_URL: $BITRISE_BUILD_URL
- BITRISE_BUILD_API_TOKEN: $BITRISE_BUILD_API_TOKEN
- BITRISE_DEPLOY_PATH: $BITRISE_DEPLOY_PATH
- NOTIFY_USER_GROUPS: $NOTIFY_USER_GROUPS
- NOTIFY_EMAIL_LIST: $NOTIFY_EMAIL_LIST
#
- STEP_VERSION: "1.2.6"
workflows:
# ----------------------------------------------------------------
# --- workflow to Step Test
test:
steps:
- script:
title: rspec
inputs:
- content: |-
#!/bin/bash
bundle install --with test
rspec .
- change-workdir:
run_if: true
inputs:
- path: ./_tmp
- is_create_path: true
- path::./:
run_if: true
inputs:
- build_url: $BITRISE_BUILD_URL
- build_api_token: $BITRISE_BUILD_API_TOKEN
- is_compress: "false"
- deploy_path: $BITRISE_DEPLOY_PATH
- notify_user_groups: $NOTIFY_USER_GROUPS
- notify_email_list: $NOTIFY_EMAIL_LIST
- is_enable_public_page: "true"
- script:
title: Output (generated by the Step) tests
inputs:
- content: |-
echo "-> BITRISE_PUBLIC_INSTALL_PAGE_URL: ${BITRISE_PUBLIC_INSTALL_PAGE_URL}"
# ----------------------------------------------------------------
# --- workflows to create Release
audit-this-step:
steps:
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
stepman audit --step-yml ./step.yml
create-release-version:
before_run:
- audit-this-step
envs:
- RELEASE_VERSION: $STEP_VERSION
steps:
- script:
title:
inputs:
- content: |
#!/bin/bash
set -ex
export CI=true
releaseman create --version $RELEASE_VERSION
publish-release:
steps:
- script:
title:
inputs:
- content: |
#!/bin/bash
set -ex
git push
git push origin tags/$STEP_VERSION
# ----------------------------------------------------------------
# --- workflow to Share this step into a Step Library
share-this-step:
envs:
# if you want to share this step into a StepLib
- MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL
- STEP_ID_IN_STEPLIB: deploy-to-bitrise-io
- STEP_GIT_VERION_TAG_TO_SHARE: $STEP_VERSION
- STEP_GIT_CLONE_URL: https://github.com/bitrise-io/steps-deploy-to-bitrise-io.git
description: |-
If this is the first time you try to share a Step you should
first call: $ bitrise share
This will print you a guide, and information about how Step sharing
works. Please read it at least once!
As noted in the Step sharing guide you'll have to fork the
StepLib you want to share this step into. Once you're done with forking
the repository you should set your own fork's git clone URL
in the `.bitrise.secrets.yml` file, or here in the `envs` section,
as the value of the `MY_STEPLIB_REPO_FORK_GIT_URL` environment.
You're now ready to share this Step, just make sure that
the `STEP_ID_IN_STEPLIB` and `STEP_GIT_VERION_TAG_TO_SHARE`
environments are set to the desired values!
To share this Step into a StepLib you can just run: $ bitrise run share-this-step
Once it finishes the only thing left is to actually create a Pull Request,
the way described in the guide printed at the end of the process.
steps:
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
bitrise share start -c ${MY_STEPLIB_REPO_FORK_GIT_URL}
bitrise share create --stepid ${STEP_ID_IN_STEPLIB} --tag ${STEP_GIT_VERION_TAG_TO_SHARE} --git ${STEP_GIT_CLONE_URL}
bitrise share finish