-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathbitrise.yml
137 lines (122 loc) · 4.08 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
format_version: "2"
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
- STEP_VERSION: 1.2.0
- IS_DEBUG: "no"
# set these in your .bitrise.secrets.yml
# set this to "yes" to run the Swift test
- IS_RUN_SWIFT_TEST: $IS_RUN_SWIFT_TEST
#
workflows:
generate_readme:
steps:
- git::https://github.com/bitrise-steplib/steps-readme-generator.git@main: {}
test:
steps:
- change-workdir:
inputs:
- path: ./_tmp
- path::./:
inputs:
- is_debug: $IS_DEBUG
- path::./:
inputs:
- content: |-
#!/bin/bash
git log -n 5 --pretty=format:"%h - %s %cr <%an>" --abbrev-commit --date=relative
exit 0
- is_debug: $IS_DEBUG
- path::./:
inputs:
- content: |-
echo "Hello, this is a Bash script!"
echo 'pwd test' > ./pwd_test.txt
# ./pwd_test.txt should be created in ./_tmp
- is_debug: $IS_DEBUG
- path::./:
inputs:
- content: |-
puts "Hello, this is a Ruby script!"
- runner_bin: ruby
- is_debug: $IS_DEBUG
- path::./:
run_if: enveq "IS_RUN_SWIFT_TEST" "yes"
inputs:
- content: |-
print("Hello Swift!")
- runner_bin: swift
- is_debug: $IS_DEBUG
- path::./:
description: |-
This version demonstrates a full Go based `go run`,
with an inline declared `go` dependency.
deps:
brew:
- name: go
inputs:
- content: |-
package main
import "fmt"
func main() {
fmt.Println("Hello, this is a Go script!")
}
- runner_bin: go run
- script_file_path: main.go
- is_debug: $IS_DEBUG
# ----------------------------------------------------------------
# --- workflows to create Release
create-release:
steps:
- script:
title:
inputs:
- content: |
#!/bin/bash
set -e
export CI=true
releaseman create --version $STEP_VERSION
# ----------------------------------------------------------------
# --- 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:
# 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: script
- STEP_GIT_VERION_TAG_TO_SHARE: $STEP_VERSION
- STEP_GIT_CLONE_URL: https://github.com/bitrise-io/steps-script.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