# Starting builds manually

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!

To start a build using the basic configuration options:

1. On the **Bitrise CI** page of your app, click the **Start build** button.

   ![scheduling-builds.png](/img/_paligo/uuid-ea158f34-25dc-4585-c7a3-0961c5ef5472.png)
1. 1. Enter the branch you want to run into the **Source branch** input field.

   You can choose between typing the name or selecting it from a dropdown menu. Click **Select branch** to bring up the dropdown menu.

   You can only set one 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.

   :::important[Pull request build]

   Starting a build of a pull request’s branch is NOT the same as a pull request build. The manually started build of a pull request branch will only build the state of the code on that branch. An automatically triggered pull request build, however, builds the state of the code as it will look like once you merged the pull request.

   :::
1. Optionally, enter a build message in the **Message** field.

   Please note that entering the Git commit message of a specific commit doesn't trigger a build of that commit!
1. From the **Target** menu, select a Workflow or Pipeline.

   If you don't select one, Bitrise will choose a Workflow or Pipeline based on your app's [trigger setup](/bitrise-ci/run-and-analyze-builds/build-triggers/yaml-syntax-for-build-triggers).

:::note[Scheduling a build]

The **Schedule this build** option allows you to configure builds to be triggered at specific times. Read more: [Scheduling builds](/bitrise-ci/run-and-analyze-builds/starting-builds/scheduling-builds).

:::

## Running Workflows from the Workflow Editor

You can manually start a build by running a single Workflow from the Workflow Editor.

To do so:

1. Open your project on Bitrise and click the **Workflows** button to open the Workflow Editor.
1. On the left, select **Workflows**, and use the dropdown menu to select the Workflow you would like to run.

   ![Workflow dropdown menu in the Workflow Editor](/img/run-and-analyze-builds/2026-07-14-workflow-editor-workflow-dropdown.png)
1. Click the **Run Workflow** button (the one with the **play** icon).

   ![Run Workflow button next to the Workflow dropdown](/img/run-and-analyze-builds/2026-07-14-workflow-editor-run-button.png)
1. Specify the branch that you want to build in the **Branch** field.

   ![Run dialog with a Branch field and Start build button](/img/run-and-analyze-builds/2026-07-14-run-workflow-branch-dialog.png)
1. Click **Start build**.

And that's it! As soon as you click the **Start build** button, your build will be kicked off, and the build's page will open in a new tab.

## Advanced configuration options for starting/scheduling builds

If you choose **Advanced** in the **Build configuration** window, you have all the options available with **Basic**, and a few more:

You can select a source type in the **Source** dropdown menu. In addition to the default **Branch** option, you can also select:

- **Tag**: Builds a particular branch or commit that is tagged with the Tag you enter. If you set this, you can't set a commit hash.

  :::important[Git Tags and commit hashes are conflicting options]

  You cannot specify both a Git Tag and a commit hash. When you set one, the other one will disappear. This ensures you cannot enter conflicting input values.

  :::
- **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. If you set this, you can't set a Git Tag.

  :::note[Commit hash takes precedence over the Branch option]

  If the **Branch** option specifies a branch where the commit hash you chose doesn't exist, Bitrise will find the branch that does have the given commit and run a build with that branch.

  :::

![start-build-advanced.png](/img/_paligo/uuid-67f3a4f0-9315-bec3-0ea7-cca80d77b103.png)

In addition to different sources, you can also add:

- **Priority**: Determines the priority of your build in the build queue. The higher the number, the sooner your build will run. The priority must be an integer between -100 and 100. The default value is 0. For more information, check out [Build priority](/bitrise-ci/configure-builds/configuring-build-settings/build-priority).
- **Custom Environment Variables**: Create a custom Environment Variable that is used in the build. See [Setting a custom Env Var when starting a build](/bitrise-ci/configure-builds/environment-variables#setting-a-custom-env-var-when-starting-a-build).
- **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.

## Rebuilding failed builds

Another way of starting a build manually is to rebuild a failed build. You can:

- Rebuild a Workflow build: [Rebuilding a failed Workflow build](/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/rebuilding-a-failed-build#rerunning-a-failed-workflow-build).
- Rebuild a Pipeline, either the entire Pipeline or only unsuccessful Workflows: [Rebuilding a failed Pipeline](/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/rebuilding-a-failed-build#rebuilding-a-failed-pipeline).
- Rebuild with remote access: [Remote access](/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/remote-access).
