Basic Build Operations

    You are viewing documentation for a release that is no longer supported. The latest supported version of version 3 is [3.11]. For the most recent version 4, see

    Manually start a new build from an existing build configuration in your current project using the following command:

    Re-run a build using the flag:

    1. $ oc start-build --from-build=<build_name>

    Specify the --follow flag to stream the build’s logs in stdout:

      Specify the --env flag to set any desired environment variable for the build:

      1. $ oc start-build <buildconfig_name> --env=<key>=<value>

      Rather than relying on a Git source pull or a Dockerfile for a build, you can can also start a build by directly pushing your source, which could be the contents of a Git or SVN working directory, a set of prebuilt binary artifacts you want to deploy, or a single file. This can be done by specifying one of the following options for the start-build command:

      When passing any of these options directly to the build, the contents are streamed to the build and override the current build source settings.

      For example, the following command sends the contents of a local Git repository as an archive from the tag v2 and starts a build:

      Manually cancel a build using the web console, or with the following CLI command:

      Cancel multiple builds at the same time:

      1. $ oc cancel-build <build1_name> <build2_name> <build3_name>

      Cancel all builds created from the build configuration:

      1. $ oc cancel-build bc/<buildconfig_name>

      Cancel all builds in a given state (for example, new or pending), ignoring the builds in other states:

      1. $ oc cancel-build bc/<buildconfig_name>  --state=<state>

      Delete a BuildConfig using the following command:

      1. $ oc delete bc <BuildConfigName>

      This will also delete all builds that were instantiated from this BuildConfig. Specify the --cascade=false flag if you do not want to delete the builds:

      You can view build details with the web console or by using the oc describe CLI command:

        This displays information such as:

        • The build source

        • The build strategy

        • The output destination

        • Digest of the image in the destination registry

        If the build uses the Docker or Source strategy, the output also includes information about the source revision used for the build, including the commit ID, author, committer, and message.

        You can access build logs using the web console or the CLI.

        To stream the logs using the build directly:

        1. $ oc logs -f build/<build_name>

        To stream the logs of the latest build for a build configuration:

          To return the logs of a given version build for a build configuration:

          1. $ oc logs --version=<number> bc/<buildconfig_name>

          Log Verbosity

          To enable more verbose output, pass the BUILD_LOGLEVEL environment variable as part of the sourceStrategy or dockerStrategy in a BuildConfig:

          Available log levels for Source builds are as follows: