Oracle Cloud Infrastructure Documentation

Running a Build

Trigger the build process by manually running a DevOps build pipeline.

You can also automatically trigger a build run when you commit your changes to the code repository.

Each service in Oracle Cloud Infrastructure (OCI) integrates with Identity and Access Management (IAM) for authentication and authorization. To grant users permission to access the DevOps build pipelines and other resources, you have to create dynamic groups and IAM policies.

For creating dynamic groups and policies for build pipelines, see Build Pipeline Policies. For more details, see DevOps IAM Policies.

Before you start the run, you must have a build pipeline defined. To run build pipelines, you must enable logging for the DevOps project. To enable logging, see DevOps Logs.

For accessing DevOps using the Oracle Cloud Console, REST API, and CLI, see Accessing DevOps.

Build Run Workflow

When a build run starts, a directed acyclic graph (DAG) is provided along with the build run progress and log details. This graph of all the linked stages in the pipeline gives a preview of all the stages that are eligible to run. During the build run, each stage that is running is highlighted in the graph. A build run is successful if all the stages in the pipeline are completed successfully.

While the build is running, the progress is tracked; after completion, a history of the actions taken is maintained. When the build run completes, you can view the run status and run progress of each build pipeline stage.

    1. Open the navigation menu and click Developer Services. Under DevOps, click Projects.
    2. Select a project and a build pipeline associated with that project.
    3. Click Start Manual Run.
    4. Accept the default name entered for the build run, or change it.
    5. Review the defined parameters for the build pipeline. If necessary, you can update the parameter values. For more information, see Configuring Parameters.
    6. (Optional) To select a specific commit that can be used to trigger the build run, click Show advanced options. Select a repository based on the source connection type and select a required branch and commit.
      By default, the manual run uses the latest commit to the code repository that was added to the build.
    7. Click Start Manual Run.

    The progress and status of the run are displayed in the Build Run tab. You can stop an in-progress run before it completes, by clicking Stop run. Note the reason for stopping the run. To view build run details including the build output, click the Menu icon at the top-right corner.

    If you have initiated a vulnerability audit for your code commit, then you can view the audit summary by clicking the Vulnerability audit section on the Build run details page. For troubleshooting, see Vulnerability Audit Failure.

  • To run a build pipeline, run the create command:

    oci devops build-run create --build-pipeline-id

    To update a build run, use the update command:

    oci devops build-run update --build-run-id

    To cancel a build run, use the cancel command:

    oci devops build-run cancel --build-run-id --reason

    To get all the commands for build-run:

    oci devops build-run -h

  • To run a build pipeline, use the CreateBuildRun operation.

    To update a build run, use the UpdateBuildRun operation.

    To cancel a build run, use the CancelBuildRun operation.