Skip to main content

Scheduling builds

Abstract

You can schedule your builds to run automatically at a specific time of the week.

You can schedule your builds to run automatically at a specific time of the week so that you can check your logs when it’s most convenient for you.

When scheduling a build, you can define custom Environment Variables. You can also set advanced filters for Git Tags and for Git commit hash.

If you have one or more regularly scheduled builds, you can:

  • Edit their configuration.

  • Trigger them manually at any time.

  • Temporarily disable them.

  • Permanently delete them.

Scheduling a build

How to schedule a build with the basic configuration options on Bitrise:

  1. Go to your Dashboard and select the app you need.

  2. Select Start/Schedule a Build.

    This opens the Build configuration pop-up window.

  3. In the Build configuration pop-up window, toggle the switch to the right to enable Schedule this build feature.

    Scheduling your builds
  4. Set the hour and minute in the HH/MM field.

    Time format and time zones in scheduled builds

    Bitrise uses the 24-hour time format when scheduling builds. The time you set on the Web UI is based on your own time zone, which is then converted and stored as UTC. If team members from other time zones access the scheduled build, they will see the time in their own time zone as well.

  5. On the timeline, select the day(s) when you want your build to run.

    Scheduling your builds
  6. Use the Time zone drop-down menu to set the time zone of your scheduled builds.

    timezone_selector.png

    Daylight saving time

    Your scheduled builds automatically adjust between standard time and daylight saving time. So, if you have scheduled your builds to trigger every day at 4 PM, they will trigger at 4 PM before switching to daylight saving time and after switching to daylight saving time. The same applies the other way around.

  7. Enter the branch you want to run into the Branch input field.

    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.

    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.

  8. 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!

  9. Select a Workflow that will run from the Workflow menu.

    If you don't select one, Bitrise will choose a Workflow based on your app's trigger map

  10. Click Schedule Build at the bottom of the pop-up window.

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:

  • Git 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.

    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.

    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.

  • Custom Environment Variables: Create a custom Environment Variable that is used in the build. See 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.

Editing a scheduled build

To change the configuration of a regularly scheduled build:

  1. Go to the Builds tab of your app.

  2. On the top, you should see a list of your scheduled builds.

  3. Click Show scheduled.

    checking-scheduled-build.png
  4. Click the little gear icon to open the settings menu.

  5. Click Edit scheduled build.

  6. Make the changes you want and click Save changes.

Triggering a scheduled build manually

To immediately trigger a scheduled build:

  1. Go to the Builds tab of your app.

  2. On the top, you should see a list of your scheduled builds.

  3. Click Show scheduled.

    checking-scheduled-build.png
  4. Click Trigger now.

Disabling a scheduled build

To temporarily disable a regularly scheduled build:

  1. Go to the Builds tab of your app.

  2. On the top, you should see a list of your scheduled builds.

  3. Click Show scheduled.

    checking-scheduled-build.png
  4. Toggle the Enabled option.

    The build will not run until you enable it again.

Deleting a scheduled build

To permanently delete a regularly scheduled build:

  1. Go to the Builds tab of your app.

  2. On the top, you should see a list of your scheduled builds.

  3. Click Show scheduled.

    checking-scheduled-build.png
  4. Click the little gear icon to open the settings menu.

  5. Click Delete and then click Delete again when prompted for confirmation.