Steps are the heart of Bitrise. A Step is a build task: for example, the Git Clone Step clones your Git repository at the start of a build while the Google Play Deploy Step can deploy your finished app to the Play Store.
A Step contains the code that performs the build task. You can configure the inputs and parameters that define the task, and view and reuse the outputs a Step generates. Reusing the output means that another Step can use it as the value of one of its inputs.
Our Steps are defined in YAML format, and written in either bash or Go. Check out our in-depth guide about how our Steps work.
You can find and check out all our available Steps at any of three locations:
For the purposes of your builds, Steps can be managed directly from the Workflow Editor. You can rearrange them, set their versions, add or remove Steps at any time.
Read on to find out more about working with our Steps!
Would you like to contribute to our enormous Step Library with your own Step? Check out our guides at For Contributors.
The configuration format of the Bitrise CLI is referred to as bitrise.yml. This is the expected file name the configuration should be saved with.
A Step encapsulates a "build task": the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.
A Workflow is a collection of steps, environment variables, and other configurations for a single bitrise run.