Is it possible to test a step directly on bitrise.io?

Question & Answer
1

I want to perform a step that is a variation of an existing step.

So, instead of loading CLI/docker enviroment, develop it all, then make request to bitrise.io, is it possible for me to make changes on my fork and on the workflow editor directly point to the relevant github commit/branch/tag ?

2

Thanks for the question @sb_ronaldopace! :wink:

Sure it is possible!

From https://github.com/bitrise-steplib/step-template#how-to-contribute-to-this-step :

Run/test the step before sending a PR or sharing it into the StepLib:

  • You can also test the step in your bitrise project, either on your Mac or on bitrise.io
  • You just have to replace the step ID in your project’s bitrise.yml with either a relative path, or with a git URL format
  • (relative) path format:
    • instead of: - original-step-id:
    • use: - path::./relative/path/of/script/on/your/Mac:
  • direct git URL format:
    • instead of: - original-step-id:
    • use: - git::https://github.com/user/step.git@branch:
  • You can find more example of alternative step referencing at: https://github.com/bitrise-io/bitrise/blob/master/_examples/tutorials/steps-and-workflows/bitrise.yml

So, e.g. if you’d want to replace the script step in your workflow:

my_workflow:
  steps:
  - script:
      inputs:
      - content: echo Hello World

You can reference the Script step’s git (https://github.com/bitrise-io/steps-script) directly, in the format:

my_workflow:
  steps:
  - git::https://github.com/bitrise-io/steps-script.git@master:
      inputs:
      - content: echo Hello World

Of course, this works for any step, even for those which are not (yet) shared in the StepLib.

1 Like
3

That’s awesome!
Thanks a lot!

1 Like