-
Notifications
You must be signed in to change notification settings - Fork 2
/
bitrise.yml
108 lines (99 loc) · 4 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
format_version: 4
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
# define these in your .bitrise.secrets.yml
- MAGIC_POD_API_TOKEN: $MAGIC_POD_API_TOKEN
- ORGANIZATION_NAME: $ORGANIZATION_NAME
- PROJECT_NAME: $PROJECT_NAME
- TEST_SETTINGS_NUMBER: $TEST_SETTINGS_NUMBER
- TEST_SETTINGS: $TEST_SETTINGS
- APP_PATH: $APP_PATH
- WAIT_FOR_RESULT: $WAIT_FOR_RESULT
- WAIT_LIMIT: $WAIT_LIMIT
- DELETE_APP_AFTER_TEST: $DELETE_APP_AFTER_TEST
- BASE_URL: $BASE_URL
# If you want to share this step into a StepLib
- BITRISE_STEP_ID: magic-pod
- BITRISE_STEP_VERSION: "0.53.0"
- BITRISE_STEP_GIT_CLONE_URL: https://github.com/Magic-Pod/bitrise-step-magic-pod.git
- MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL
workflows:
test:
steps:
- go-list:
- 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: Step Test
run_if: true
inputs:
- magic_pod_api_token: $MAGIC_POD_API_TOKEN
- organization_name: $ORGANIZATION_NAME
- project_name: $PROJECT_NAME
- test_settings_number: $TEST_SETTINGS_NUMBER
- test_settings: $TEST_SETTINGS
- app_path: $APP_PATH
- wait_for_result: $WAIT_FOR_RESULT
- wait_limit: $WAIT_LIMIT
- delete_app_after_test: $DELETE_APP_AFTER_TEST
- base_url: $BASE_URL
- script:
inputs:
- content: |
#!/bin/bash
echo "This output was generated by the Step (MAGIC_POD_TEST_SUCCEEDED): $MAGIC_POD_TEST_SUCCEEDED"
echo "This output was generated by the Step (MAGIC_POD_TEST_RESULT): $MAGIC_POD_TEST_RESULT"
# ----------------------------------------------------------------
# --- workflows to Share this step into a Step Library
audit-this-step:
steps:
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
stepman audit --step-yml ./step.yml
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
- 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