Bitrise.io public repositories & issues
Fun and simple development automation
The purpose of this repository is to keep track of the most important public repositories related to bitrise.io.
If you want to suggest a new feature, you can submit it and vote on others' on discuss.bitrise.io/c/feature-requests, or if you want to chat with us and the Bitrise Community you can join discuss.bitrise.io or Slack at chat.bitrise.io. Follow @bitrise on Twitter for #status and step updates
Report an issue / bug
If you want to report an issue you can do that by creating a GitHub issue in the related repository.
- If it's related to a specific Step, you should report it on the Step's GitHub page.
- If it's a build issue, please report it at: discuss.bitrise.io/c/issues/build-issues
- If it's related to the Bitrise CLI you can do that on the Bitrise CLI's GitHub page.
- If you want to share private information with us, please contact us through email or through the on-site chat on bitrise.io (You have to be logged in to see the chat icon at the bottom right corner. Note: some Ad Blockers might block the chat widget).
Contribution to Bitrise (stack, tools & steps)
If you want to collaborate with us creating useful automation tools and steps please go to the
contrib repository and follow the guides. You can keep track of others' projects there as well.
Our build steps collection
A step is a script with a corresponding
yml that conforms to the formatting and naming conventions of the StepLib.
You can find all our steps'
ymls under /steps.
The repositories of the steps which we maintain and provide support for can be found by searching for steps- in our bitrise-io GitHub organization, the newer ones in the bitrise-steplib GitHub organization, and the ones we maintain with the community in the bitrise-community GitHub organization.
We have most of our scripts written in
bash, but it's possible to write it in any language our machines have installed, like
You can create a StepLib independently from Bitrise anytime, you will be able to use our CLI tools to maintain it, they are not tied to our StepLib.
Bitrise CLI tools
Check out our CLI's page for a nice intro about why is it helpful to have Bitrise installed on your machine.
The runner itself, you can install it to your machine with Homebrew:
brew update && brew install bitrise
curl down the latest version with the help of our guide on the releases page.
envman is our handy environment variable manager for switching between environment sets quick & easy.
stepman is our solution to manage decentralized StepLib step (script) collections.
You will run into
stepman directly most probably when you are sharing your own step to a StepLib.
We have a collection of useful tools under the bitrise-io account. Not all of them part of the Bitrise CLI family, but are connected to our technology.
All Bitrise CLI tools are written in Go.
You can find all of our bootstrap scripts on the OS X bootstrap GitHub page.
When a new version of a stack is available there will be a system report generated under the system_reports folder of this repository.
Request a tool to be pre-installed on a build machine
- For OS X you can create an issue or pull request at
- For our Docker based stack you can create an issue or pull request at:
List of official Bitrise organizations on GitHub
Aggregated Issue and Pull Request lists
Aggregated Issue and Pull Request lists, related to the Bitrise CLI tools, stacks and official steps (You have to be logged in on GitHub to be able to access the aggregated lists / searches):
- Open Pull Requests across the Bitrise CLI tools, stacks and official steps
- Open Issues across the Bitrise CLI tools, stacks and official steps
Check out our sample app repositories.
- Xcode 7 sample project (with UI Testing)
- Quick sample project
- XCTest sample project
- Specta sample project
- Kiwi sample project
Or simply search our GitHub account page for sample- to see all of our sample projects.