-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbitrise.yml
96 lines (86 loc) · 3.7 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
format_version: 1.1.0
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
# define these in your .bitrise.secrets.yml
- AWS_ACCESS_KEY: $AWS_ACCESS_KEY
- AWS_SECRET_KEY: $AWS_SECRET_KEY
- AWS_REGION: $AWS_REGION
- DEVICE_FARM_PROJECT: $DEVICE_FARM_PROJECT
- DEVICE_FARM_UPLOAD_FILE_PATH: $DEVICE_FARM_UPLOAD_FILE_PATH
- DEVICE_FARM_UPLOAD_FILE_TYPE: $DEVICE_FARM_UPLOAD_FILE_TYPE
workflows:
# ----------------------------------------------------------------
# --- workflow to Step Test
test:
steps:
- path::./:
inputs:
- access_key_id: $AWS_ACCESS_KEY
- secret_access_key: $AWS_SECRET_KEY
- device_farm_project: $DEVICE_FARM_PROJECT
- upload_file_path: $DEVICE_FARM_UPLOAD_FILE_PATH
- upload_type: $DEVICE_FARM_UPLOAD_FILE_TYPE
- aws_region: $AWS_REGION
- script:
inputs:
- content: |-
#!/bin/bash
set -ex
if [[ ! -z "$BITRISE_DEVICEFARM_UPLOAD_ARN" ]]; then
echo "Got upload ARN: $BITRISE_DEVICEFARM_UPLOAD_ARN"
else
echo "Did not get upload ARN" 1>&2
exit 1
fi
# ----------------------------------------------------------------
# --- workflow 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:
- MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL
- STEP_ID_IN_STEPLIB: aws-device-farm-file-deploy
- STEP_GIT_VERION_TAG_TO_SHARE: 0.0.4
- STEP_GIT_CLONE_URL: https://github.com/peartherapeutics/bitrise-aws-device-farm-file-deploy.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.
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 ${STEP_ID_IN_STEPLIB} --tag ${STEP_GIT_VERION_TAG_TO_SHARE} --git ${STEP_GIT_CLONE_URL}
bitrise share finish
# Automatically generate pull request using hub tool if present
if hash hub 2>/dev/null; then
echo 'Creating PR...'
collections_folder="$HOME/.stepman/step_collections"
newest_collection=$(ls -1 "$collections_folder" | tail -n 1)
cd "${collections_folder}/${newest_collection}/collection"
echo -ne "$STEP_ID_IN_STEPLIB $STEP_GIT_VERION_TAG_TO_SHARE\n\n" | cat - PULL_REQUEST_TEMPLATE.md | hub pull-request -b bitrise-io/bitrise-steplib:master -F -
fi