-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathbitrise.yml
More file actions
executable file
·130 lines (113 loc) · 4 KB
/
bitrise.yml
File metadata and controls
executable file
·130 lines (113 loc) · 4 KB
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
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
- SAMPLE_APP_REPOSITORY_URL: https://github.com/bitrise-samples/android-sdk21-tools-21.0.1.git
- SAMPLE_APP_CLONE_INTO_DIR: ./_tmp/android-sdk21-tools-21.0.1
workflows:
# ----------------------------------------------------------------
# --- workflow to Step Test
test:
steps:
- script:
title: Print go environment
inputs:
- content: |-
set -x
go version
echo $GO15VENDOREXPERIMENT
- script:
title: Export GOPATH
inputs:
- content: |-
set -x
envman add --key GOPATH --value "$BITRISE_SOURCE_DIR/go"
- script:
title: "Go Test"
inputs:
- working_dir: $BITRISE_SOURCE_DIR/go/src/github.com/bitrise-io/install-missing-android-tools
- content: |
set -ex
go test ./...
- script:
title: Step audit
inputs:
- content: stepman audit --step-yml=./step.yml
- script:
title: Git clone sample app
inputs:
- content: |
#!/bin/bash
set -e
set -x
if [ -e $SAMPLE_APP_CLONE_INTO_DIR ] ; then
rm -rf $SAMPLE_APP_CLONE_INTO_DIR
fi
git clone $SAMPLE_APP_REPOSITORY_URL $SAMPLE_APP_CLONE_INTO_DIR
- change-workdir:
title: Switch working dir
run_if: true
inputs:
- path: $SAMPLE_APP_CLONE_INTO_DIR
- path::./:
title: Step test
# ----------------------------------------------------------------
# --- workflows to create Release
create-release:
steps:
- script:
title:
inputs:
- content: |
#!/bin/bash
set -e
export CI=true
releaseman create --bump-version patch
create-release-version:
envs:
- RELEASE_VERSION: 0.9.0
steps:
- script:
title:
inputs:
- content: |
#!/bin/bash
set -e
export CI=true
releaseman create --version $RELEASE_VERSION
# ----------------------------------------------------------------
# --- workflows 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: install-missing-android-tools
- STEP_GIT_VERION_TAG_TO_SHARE: 0.9.0
- STEP_GIT_CLONE_URL: https://github.com/bitrise-steplib/steps-install-missing-android-tools.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 -e
set -x
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