-
Notifications
You must be signed in to change notification settings - Fork 11
/
bitrise.yml
76 lines (67 loc) · 2.95 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
format_version: "4"
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
app:
envs:
# An example secret param, define it (A_SECRET_PARAM) in .bitrise.secrets.yml
- STEP_VERSION: 2.1.0
# If you want to share this step into a StepLib
- BITRISE_STEP_ID: microsoft-teams-integration
- BITRISE_STEP_VERSION: "2.1.0"
- BITRISE_STEP_GIT_CLONE_URL: https://github.com/amrfarid140/bitrise-step-microsoft-teams-integration.git
- MY_STEPLIB_REPO_FORK_GIT_URL: https://github.com/amrfarid140/bitrise-steplib.git
workflows:
test:
steps:
- go-list: {}
- golint: {}
- errcheck: {}
- go-test: {}
- path::./:
title: Step Test
run_if: "true"
inputs:
- webhook_url: https://outlook.office.com/webhook/5bdfe871-8b29-47d0-82dc-4fd42e02d0b9@dacd0a8f-30ed-4ee0-ad06-de7c7aa659ed/IncomingWebhook/6bcb8d7d07e04dc5880a0830c1e861a0/a05f31c9-bb92-46a8-bbdb-371c36e8902c
# ----------------------------------------------------------------
# --- 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