This section describes how buddybuild builds your projects.


Here is a high-level summary of buddybuild’s build process:

  1. Trigger
    A build can be triggered in several ways:

    • whenever you push new commits to your repository,

    • whenever a pull request is created in your repository,

    • on a schedule,

    • manually in the buddybuild dashboard.

  2. Evaluation
    Once a build is triggered, buddybuild evaluates the build configuration to determine whether to skip a build, auto-cancel a build (for any queued or in-progress builds of the same branch), or to build selectively.

  3. Queue
    Once buddybuild determines that a build should proceed, it is queued according to your plan level, and is executed as soon as an appropriate build resource is available. Builds are typically queued for only a few seconds.

  4. Execution
    Once a build resource starts working on your build, the following steps are taken:

    1. Prepare the build environment according to build configuration.

    2. Clone your app’s source code from your repository.

    3. Retrieve device variables, environment variables, and secure files from secure storage.

    4. Resolve your app’s dependencies.

    5. Perform build steps, including executing tests for successful builds, and any custom steps that may be defined.

  5. Finish up
    After the build is complete, whether it is successful or not, the following steps are taken:

    • Securely store build artifacts, including logs.

    • Send notifications.

    • For successful builds, deploy the build to testers (unless disabled).

results matching ""

    No results matching ""