Starting a build manually on Bitrise takes literally two clicks - if you leave everything on the default settings. If you do not wish to do that, or at least want to be sure what the default settings are, read on! We’ll walk you through the process.
- Log in to Bitrise and go to the Dashboard.
- Select the app you wish to build.
Click Start/Schedule a Build.
At this point, the Build configuration window opens and you are presented with two tabs near the top of the window:
Basic configuration ⚓
If you choose Basic in the Build configuration window, you have three options to configure:
- Branch: The Git branch that you wish to build. Make sure to type the name of the branch correctly, otherwise the build will fail. You can only enter a single branch. If a pull request to your repository is made from a forked branch, type the name of that branch to run a build of the pull request.
- Message: The build message. Please note that entering the Git commit message of a specific commit does not trigger a build of that commit!
- Workflow: This is an optional setting. You can select the workflow you wish to run. By default, it is based on the trigger map: for example, if you wish to run the
testbranch, and the
testbranch is configured in the trigger map to trigger the
testingworkflow. You can configure the trigger map either on the website or directly in the bitrise.yml of the app.
Advanced configuration ⚓
If you choose Advanced in the Build configuration window, you have all the options available with Basic, and a few more:
- Git Tag: Builds a particular branch or commit that is tagged with the Tag you enter.
- Commit Hash: Copy a specific commit’s hash here to build that particular commit. This option can even send a build status update to your git hosting service.
- Custom Environment Variables: Set up a custom Environment Variable that is used in the build. You can enable the Replace variables in input? option: this replaces the Environment Variables in your input with the assigned value. You need to do this if your custom variable references other Environment Variables. Be aware that if you specify the same key that an App Environment Variable already has, the latter will take precedence - in other words, if your custom Env Var has the same key but a different value than an App Env Var, the build will use the App Env Var.
- Generated cURL command: Based on the options you set in the Build configuration window, we provide an automatically generated cURL command. This can be copied and pasted, and you can run it on any platform that has cURL installed.