FilesExpand file tree

main

/

bitrise.yml

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

100 lines (90 loc) · 3.71 KB

main

/

bitrise.yml

Copy path

Top

File metadata and controls

• Code
• Blame

100 lines (90 loc) · 3.71 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

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

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

- A_SECRET_PARAM: $A_SECRET_PARAM

# If you want to share this step into a StepLib

- BITRISE_STEP_ID: xcui-browserstack-official

- BITRISE_STEP_VERSION: "1.0.0"

- BITRISE_STEP_GIT_CLONE_URL: https://github.com/browserstack/browserstack-bitrise-xcui-step.git

- MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL

workflows:

test:

steps:

- script:

inputs:

- content: |

#!/bin/bash

echo "Just an example 'secrets' print."

echo "The value of 'A_SECRET_PARAM' is: $A_SECRET_PARAM"

- 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

description: |-

The example input has a default value,

you can overwrite it if you want to, just like we did below,

but the step would use the default value specified in the `step.yml`

file if you would not specify another value.

run_if: true

inputs:

- example_step_input: Example Step Input's value

- script:

inputs:

- content: |

#!/bin/bash

echo "This output was generated by the Step (EXAMPLE_STEP_OUTPUT): $EXAMPLE_STEP_OUTPUT"

# ----------------------------------------------------------------

# --- 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