-
Notifications
You must be signed in to change notification settings - Fork 7
/
bitrise.yml
172 lines (160 loc) · 6 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
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
---
format_version: 4
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
- YOUR_API_KEY: "$YOUR_API_KEY"
- APP_OWNER_NAME: "$APP_OWNER_NAME"
- APP_PATH: "$APP_PATH"
- TEST_PAID_API_KEY: "$TEST_PAID_API_KEY"
- TEST_PAID_OWNER_NAME: "$TEST_PAID_OWNER_NAME"
- TEST_DISTRIBUTION_KEY: "$TEST_DISTRIBUTION_KEY"
- BITRISE_STEP_ID: deploygate--upload-app-bitrise-step
- BITRISE_STEP_GIT_CLONE_URL: https://github.com/DeployGate/upload-app-bitrise-step.git
- MY_STEPLIB_REPO_FORK_GIT_URL: https://github.com/DeployGate/bitrise-steplib
- BITRISE_STEP_VERSION: 1.1.3
workflows:
on_local:
steps:
- change-workdir:
title: Switch working dir to run `deploygate--upload-app-bitrise-step`
description: |
Please provide the workspace which the step can make dirty.
The step will create some intermediate files in the workspace.
run_if: true
inputs:
- path: "./_tmp"
- is_create_path: true
- path::./:
title: Upload an application
description: 'This is a sample upload
'
run_if: true
inputs:
- api_key: "$YOUR_API_KEY"
- owner_name: "$APP_OWNER_NAME"
- app_path: "$APP_PATH"
- message: via Bitrise CLI test
test:
steps:
- change-workdir:
title: Switch working dir to test / _tmp dir
description: |-
To prevent step testing issues, like referencing relative
files with just './some-file' in the step's code, which would
work for testing the step from this directory directly
but would break if the step is included in another `bitrise.yml`.
run_if: true
inputs:
- path: "./_tmp"
- is_create_path: true
- path::./:
title: Upload an application w/o extra parameters
description: 'Upload an application w/o extra parameters
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.apk"
- message: via Bitrise CLI test
- script:
title: Check if the previous step has added a response to envman properly
run_if: true
inputs:
- content: |
#!/bin/bash
set -eu
echo "The response was: $DEPLOYGATE_UPLOAD_APP_STEP_RESULT_JSON"
- path::./:
title: Upload an application with a short message
description: 'Upload an application with a short message
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.apk"
- message: via Bitrise CLI test
- path::./:
title: Upload an application with a distribution name
description: 'Upload an application with a distribution name
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.apk"
- distribution_name: BITRISE_CLI_TEST
- path::./:
title: Upload an application with a distribution key
description: 'Upload an application with a distribution key
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.apk"
- distribution_key: "$TEST_DISTRIBUTION_KEY"
- path::./:
title: Upload an application with a release note
description: 'Upload an application with a distribution release ntoe
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.apk"
- distribution_name: BITRISE_CLI_TEST
- release_note: Can you see me?
- path::./:
title: Upload an application with disabling notififications
description: 'Upload an application with disabling notififications
'
run_if: true
inputs:
- api_key: "$TEST_PAID_API_KEY"
- owner_name: "$TEST_PAID_OWNER_NAME"
- app_path: "../fixture/sample.ipa"
- disable_notify: 'true'
audit-this-step:
steps:
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
stepman audit --step-yml ./step.yml
share-this-step:
envs:
- MY_STEPLIB_REPO_FORK_GIT_URL: "$MY_STEPLIB_REPO_FORK_GIT_URL"
- BITRISE_STEP_ID: "$BITRISE_STEP_ID"
- BITRISE_STEP_VERSION: "$BITRISE_STEP_VERSION"
- BITRISE_STEP_GIT_CLONE_URL: "$BITRISE_STEP_GIT_CLONE_URL"
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 `BITRISE_STEP_ID` and `BITRISE_STEP_VERSION`
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.
before_run:
- audit-this-step
steps:
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
bitrise share start -c "${MY_STEPLIB_REPO_FORK_GIT_URL}"
bitrise share create --stepid "${BITRISE_STEP_ID}" --tag "${BITRISE_STEP_VERSION}" --git "${BITRISE_STEP_GIT_CLONE_URL}"
bitrise share finish