Migrate from Jenkins to Bitrise

Japanese translation unavailable

This page has not been translated into Japanese yet - we apologise for the inconvenience! If you’re interested in helping us out, feel free to translate any article in the jp folder of the DevCenter repository and open a PR!

このページは日本語への翻訳がまだ完了しておりません。ご不便をおかけして申し訳ございません! もしお手伝いできる方がいらっしゃれば、ご自由にjpフォルダの記事を日本語に訳していただき、PRを開いてください

If you have been looking to switch from Jenkins to Bitrise to speed up your mobile CI/CD flow and ease dedicated manpower, look no further. This guide introduces the most important Bitrise features and how you can quickly settle into Bitrise from your Jenkins world.

Why bother migrating?

Jenkins is a self-hosted CI server where you have to manually install and maintain most of the functionalities before you could run any build and also requires dedicated manpower for regular maintenance. When you switch to Bitrise, you get to experience the comfort of using a cloud-based, mobile first CI/CD platform which offers out-of-the box functionalities for all your mobile development needs on one platform. This means there is:

Bitrise takes care of all of the above. We have a vast array of automatized Steps, API, CLI, up-to-date Stacks and add-ons with a highly intuitive GUI, called Workflow Editor, all available at your fingertips.

Check out the world of automated mobile development with Bitrise!

Looking for more evidence on how Bitrise helped other companies switching from Jenkins?

Projects on Jenkins and Bitrise

A project on Bitrise is the synonym of an application. When you add an app to Bitrise, you connect your Git repository to Bitrise. Then the Bitrise project scanner detects your project type and crafts a default configuration. Once the process completes, your project is available on Bitrise. From this point on, we call it an app.

Most Jenkins users work with Jenkins Pipeline or Freestyle project (besides other available project types). There is no such project difference in Bitrise. Every time you connect an app to Bitrise, we automatically create a basic configuration file, called bitrise.yml, and immediately trigger a build with that configuration. Should you need to modify your project’s repository URL (due to, for example, a repository name or URL change) you can easily change it on your app’s Settings page.

When using Jenkins, you can configure your Pipeline or Freestyle project, through the classic UI, to some extent, or more so through the Blue Ocean plugin or directly through the Jenkinsfile. To get a more enjoyable developer experience, you might lean onto using Blue Ocean, depending on your preference. If using the Blue Ocean plugin, you first have to install it. In Bitrise, there is no need to install anything to enjoy an intuitive, mobile developer friendly UI that visualizes your Workflow with the necessary tools right off the bat.

Out-of-box support for platforms

Bitrise supports native and cross-platform apps out-of-the-box and detects your project type automatically: iOS, Android, Ionic / Cordova, React Native, Flutter, Xamarin, MacOS, and Expo. No need to painfully select and install machines and plugins to run your preferred app type.

Check out your apps listed under APPS on your Dashboard.

Your code is safe with us

To guarantee the security of your builds we use clean virtual machines for every builds. This means that every build runs on its own, clean virtual machine and we discard the whole virtual machine after the build finishes, erasing every file your build (except for artifacts) uses and every change you make during your build. Learn more about code security.

Quick Start Guide

This Quick Start Guide helps you start your first build on Bitrise with minimum config.

  1. Sign up to Bitrise if you don’t have an account yet.
  2. Connect a repo and run an automatically configured standard Workflow on any project.
  3. Once you’ve looked through the generated YML, make the changes you need: if you’re opting for a custom code, pop it into our Script Step, and run your first build. Or find the Steps in our Step Library to replicate your Jenkinsfile’s behaviors.
  4. After getting to your new Workflow’s first green build, setup other jobs based on, for example, triggers and scheduled builds.
  5. Optimize your Workflows with Steps like Cache Pull and Cache Push.
  6. Need help? Contact us.

If you are interested in the main Jenkins-Bitrise differences and how Bitrise enhance your mobile development process, then continue with the guide below.

Managing Builds in Jenkins and Bitrise

A build on Bitrise is the process specified by the app’s Workflow. It is a series of Steps, defined in a Workflow, executed by the Bitrise CLI on a clean virtual machine or locally on your machine. You can check your app’s builds on the Bitrise Dashboard or analyze your build log on your app’s own Builds page. If you’re looking to view or download your artifacts after a successful build run, check out build artifacts online.

Let’s see what you can do with builds on Bitrise:

Triggering builds on Jenkins and Bitrise

In this section we describe how you can trigger builds on Bitrise:

Environment Variables and Secrets

Environment Variables (a key and value pair) can be defined on app, Workflow and Steps level. There are certain Env Vars that are exposed by the Bitrise CLI and ones which are only exposed by

There are a bunch of cool stuff you can do with Env Vars, for example:

Secrets are a type of Environment Variables but special ones. They hide sensitive information in an encrypted format so that your private input is not exposed in the build logs or in the bitrise.yml. Secret Environment Variables, or Secrets in short, can be set by adding a key and the variable in the Secrets tab of the Workflow Editor. This is again a built-in feature of Bitrise which ensures the following:

Learn more about Secrets:


Every build on Bitrise runs on a clean virtual machine but it does not mean you have to do everything from scratch - you can cache contents of important files and preserve them between builds.

Learn more about builds in Bitrise.

Jenkins plugins and Bitrise Steps

A Step is a pre-defined task in Bitrise just like the Jenkins Steps, however, a Bitrise Step can be easily configured on our intuitive UI or you can even pull in your own Step from your repository. You can configure the inputs and parameters that define a Step task, and view/reuse the outputs a Step generates. Reusing the output means that another Step in the same Workflow can use it as the value of one of its inputs.

Advantage of using Bitrise Steps

As being a continuous integration tool itself, Jenkins integrates with other services with the help of plugins. Jenkins users have to manage plugins in a centralized place, called Manage plugins, install them globally (on their Jenkins server), then use them in their specific projects. If Jenkins notifies of a newer plugin version, Jenkins admins have to doublecheck with their teams if they’re running any builds since updating a plugin requires the server to restart. With Jenkins plugins, reverting to an older version is not possible, since only the latest version is available. In Bitrise, however, you do not have to install any Steps first, because you can add or remove any Step in your Bitrise Workflow at any time as you wish and it won’t block any running builds of the project. You can always revert back to a previous Step version too if that’s what you need.

What’s more: When editing your Workflow in the Workflow Editor, you can easily search for a Step based on functionality or platform you are looking for in the Step Library and add it to your Workflow straightaway - there is no need to install them prior to setting up your Workflow.

You can create your own custom Step too and store in a repository, then you can reference it by a URL in your Workflow.

A Step jolly joker: our Script Step

Do you have a custom script you’d like to run in your Workflow? Select the Script Step from the Step Library and add your custom code to the Script content input. Learn more about how to configure the Step and some troubleshooting tips.

Discover our Steps on our Integrations page or right when editing your Workflow.

Learn what else you can do with Steps:

Using fastlane in Jenkins?

You can easily put your fastlane lanes to work on Bitrise too. All you have to do is add a Bitrise’s Fastlane Step to your Workflow and add your lane name into the Step. Start a build and your lane will run on Bitrise.

Jenkins Pipeline - Bitrise Workflow

A Jenkins Pipeline is equivalent to a Bitrise Workflow, but the Bitrise Workflows are much easier to manage: you can quickly create new Workflows based on existing ones, chain multiple Workflows together in a single build, or delete Workflows that you no longer need.

A Bitrise Workflow is a series of Steps, such as test, code sign, build APK/ ipa and deploy. When you add an app to Bitrise, a primary Workflow, created based on the project scanner’s findings, gets kicked off/triggered automatically.

You can have several Workflows for a certain project. For example:

Workflow Editor

The Workflow Editor is the main place for configuring your Workflow. Jenkins Stages are equal to multiple Bitrise Workflows chained together inside a main Workflow. On Bitrise the Workflow Editor helps you to chain Workflows like one would chain toy trains after each other.

The Workflow Editor has other powerful features built in to assist you with mobile development:

There’s a bunch of other Workflow management tasks you can do with Workflow, check them out:

Dashboards in Jenkins and Bitrise

This is the main landing page where you find yourself once you start your first build. If you start using Bitrise more, you will see a list of your latest, queued builds and your installed projects along with your own profile and the Workspace/s you are member of - all on one page.

The LATEST BUILDS tab on your Bitrise Dashboard displays all recent builds similarly to the Build history feature in Jenkins. You can filter for any status: successful, aborted, failed, and running but each build displays their statuses anyway.

On Jenkins, build statuses are listed in the Build Executor Status or on the Blue Ocean Dashboard. When using Bitrise you get a user-friendly graphical interface right from the start, whereas, with Jenkins, you have to install the plugin first. Bitrise build statuses are shown on both the Dashboard, and on the Builds page of your app.

Build Queue on Jenkins is the Queued Builds on Bitrise. You can schedule builds to queue them with the Advanced option of the Schedule builds feature.

On the right side of the Dashboard, you can see all your apps under APPS.

Adding a new app to Bitrise

What New item means in Jenkins, is the adding a new app flow, either by the web UI or from any CLI on Bitrise. This is a highly automated flow where minimal configuration is needed from you and literally within a minute your new build starts. Our flow takes you through all the important phases: setting privacy, connecting your repository, setting up repository access, choosing a branch, configuring your app, setting up your build configuration and setting up a webhook.


Bitrise makes extensive use of webhooks, which you can enable with a simple click when connecting an app to Bitrise. It all makes sense to add the webhook during the initial setup and not having to search for this functionality when you try to quickly get your app to speed.

Adding a GitHub webhookIn short, there are two types of Webhooks:

Jenkins plugins - Bitrise Add-ons

Add-ons are like cherry on the cake. They take Bitrise’s functionality to the next level by recruiting the already existing data on Bitrise and providing extra services in testing, deployment, monitoring, reporting, security and utility. Add-ons blend in nicely into the Bitrise ecosystem since they act as individual galaxies in the big Bitrise universe.

Bitrise add-ons don’t have to be installed and updated like Jenkins plugins - they are available out of the box and come for free. They have their own page which you can access either from the Dashboard or through your Builds page. Let’s have a closer look.

Jenkinsfile - Bitrise YAML

A Jenkins Pipeline uses groovy code, while Bitrise uses the more highly structured YAML format. All Workflows are defined in the bitrise.yml file in YAML format, which you can edit by clicking the bitrise.yml tab of the Workflow Editor.

You can store and manage the bitrise.yml file of your app either on or in your repository. Don’t worry, your secrets (for example, credentials and IDs) are safe with us.

You can also download the current bitrise.yml configuration of your app and run it locally with the Bitrise CLI.

Jenkinsfile - Bitrise yml file comparison

If you have been using a Jenkinsfile (Pipeline project) in Jenkins and and considering to switch to Bitrise, you can easily match Jenkinsfile stages with Bitrise Steps. If you have been using the old-school Freestyle project, then you have to map your configuration’s settings with a matching Bitrise Step or a Bitrise function. For example, match the Build section of your Freestyle project with a Bitrise build Step, such as the Android Build Step, or map the Build Trigger section of Jenkins with the Triggers function of Bitrise. Make sure you check out our Step Library for more inspiration.

Bitrise sample apps and their bitrise.yml files

Here you can find iOS, Android and cross-platform sample projects. Check their bitrise.yml file to understand their setup. We hope you can use them as jumping off points when crafting your first Bitrise project.

Master and agent on Jenkins - Bitrise Stacks

A stack is the type of virtual machine we use to run your build. For example, for a native iOS app, the best stack is one of our Xcode stacks. Stacks come with all of the necessary tools pre-installed, and are regularly updated to make sure they will serve all of your needs. This way you don’t have to bother with maintaining master and agent instances or adding a node machine to your groovy code to run a build on a certain platform.

How do stacks work on Bitrise?

When you add your app to Bitrise, our project selector automatically detects the type of your project and based on its platform type, adds a default stack to it. Your first build will run on this stack, which is a virtual machine with all the required tools pre-installed on it. Should you wish to use another stack, you can simply select it from the Default Stack dropdown menu on the Stack tab. If you click the More information link, you can see the preinstalled tools with their versions.

We support the latest Xcode version shortly after its official release.

System reports

In our system reports you can check the installed tools and their versions on each stack.

Learn more about our Stack update and removal policy.

People management in Jenkins and Bitrise

What you have on the People page of Jenkins can be found in two places on Bitrise (depending on if you have a team or a Workspace set up).

The purpose of Workspaces is to make it easier to manage several people working on different apps on Bitrise. Workspaces can own an unlimited number of apps, and Workspace owners can assign Workspace members to work on different apps as they see fit.

A Team on Bitrise means all the users who work on the same app: they make up the app’s team, and you can manage them on the app’s Teams tab.

On the Groups tab you can manage Workspace members such as delete, add a new member to the group, assign a group to apps and rename a group. On the People tab you can see who is already added to the Workspace and, if needed, you can remove a member from all groups of the Workspace.

Workspaces consist of groups: Workspace owners can create groups and decide which members belong to which groups. A given group can be assigned to work on an app: all members of the same group will have the same level of access to the app.

Learn more about Workspaces and Teams.

Integrated SSO management on Bitrise

While in Jenkins you have to install an authorization plugin for SSO management, in Bitrise it comes as an integral part of the Velocity plan. Workspace with such plans can set up SAML SSO as their single gateway to their Workspace on Bitrise. No more remembering usernames and credentials! All the Workspace owner has to do is set up Bitrise as a SAML SSO app on the SAML SSO provider and invite Workspace members to the Bitrise Org. We have specific guides to the different SAML SSO providers to guide you through the steps.

Learn more about SAML SSO setup:

Have some tips and tricks?

If you have some tips and tricks on migrating from Jenkins to Bitrise and you believe the rest of the community from benefit from it, leave us a pull request and we will be in touch with you.