- Home
- Workflows and Pipelines
- Workflows
- Default Workflows
Default Workflows
When you add a new app on bitrise.io, one or two Workflows are created automatically, depending on your app.
When you add a new app on bitrise.io, we create your initial Workflows for you. These are your default Workflows. You can use these to run your tests or create installable app packages such as IPAs or APKs. Feel free to modify the default Workflows to suit your needs.
Default Workflows for an iOS app
For a new iOS app, Bitrise automatically generates two Workflows. The Steps of these default Workflows depend on whether you have tests configured on your Xcode project. These Workflows are basic iOS Workflows that allow you to discover how Bitrise works. You can customize these Workflows or create new ones based on them.
|
Workflow ID |
Workflow summary |
Workflow description |
|---|---|---|
|
|
Run your Xcode tests and get the test report. |
The Workflow clones your Git repository, caches and installs your project’s dependencies if there are any, runs your Xcode tests and saves the test results. |
|
|
Builds your Xcode project. Tests not foundThis Workflow is generated only if the project scanner didn't find any tests configured in your Xcode project. |
The Workflow clones your Git repository, caches and installs your project’s dependencies if there are any, and builds your project. It uses Xcode's build for testing action. |
|
|
Run your Xcode tests and create an IPA file to install your app on a device or share it with your team. |
The Workflow clones your Git repository, caches and installs your project’s dependencies if there are any, runs your Xcode tests, and exports an IPA file from the project. |
Default Workflows for an Android app
For a new Android app, Bitrise automatically generates two Workflows: run_tests and build_apk. These are basic Android Workflows that allow you to discover how Bitrise works. You can customize these Workflows or create new ones based on them.
|
Workflow ID |
Workflow summary |
Workflow description |
|---|---|---|
|
|
Run your Android unit tests and get the test report. |
The Workflow clones your Git repository, caches your Gradle dependencies, installs Android tools, runs your Android unit tests and saves the test report. |
|
|
Run your Android unit tests and create an APK file to install your app on a device or share it with your team. |
The Workflow clones your Git repository, installs Android tools, sets the project’s version code based on the build number, runs Android lint and unit tests, builds the project’s APK file and save it. |
Default Workflows for multiplatform apps
For multiplatform apps - apps that aren't native iOS or Android apps but created with some mobile development framework, such as React Native, Flutter, Ionic or Cordova -, Bitrise creates two default Workflows: primary and deploy.
The exact Steps included in these default Workflows depend on the project type. However, the main goals of the two Workflows are the same, regardless of project type:
-
The
primaryWorkflow clones your app, installs and caches your dependencies, and runs any tests configured in the project. -
The
deployWorkflow, in addition to installing and caching dependencies and running tests, also builds your project: it tries to generate an APK or IPA file.
For more details about what the default Workflows include for different project types, try out our demo apps!
A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.
The project scanner is a tool that identifies the given project’s type and generates a basic Bitrise configuration. Each supported project type has its own scanner: these scanners are stored as separate packages.