Performing basic builds

You can manually start a new build from an existing build configuration in your current project.

Procedure

To manually start a build, enter the following command:

You can manually re-run a build using the flag.

Procedure

Streaming build logs

You can specify the --follow flag to stream the build’s logs in stdout.

Procedure

To manually stream a build’s logs in stdout, enter the following command:
```
$ oc start-build <buildconfig_name> --follow
```

Setting environment variables when starting a build

You can specify the --env flag to set any desired environment variable for the build.

Procedure

To specify a desired environment variable, enter the following command:
```
$ oc start-build <buildconfig_name> --env=<key>=<value>
```

Rather than relying on a Git source pull or a Dockerfile for a build, you 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 pre-built 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.

Procedure

$ oc start-build hello-world --from-repo=../hello-world --commit=v2

You can cancel a build using the web console, or with the following CLI command.

Procedure

To manually cancel a build, enter the following command:

Canceling multiple builds

You can cancel multiple builds with the following CLI command.

Procedure

To manually cancel multiple builds, enter the following command:
```
$ oc cancel-build <build1_name> <build2_name> <build3_name>
```

Canceling all builds

You can cancel all builds from the build configuration with the following CLI command.

Procedure

To cancel all builds, enter the following command:
```
$ oc cancel-build bc/<buildconfig_name>
```

You can cancel all builds in a given state, such as or pending, while ignoring the builds in other states.

Procedure

To cancel all in a given state, enter the following command:
```
$ oc cancel-build bc/<buildconfig_name>
```

You can delete a BuildConfig using the following command.

Procedure

To delete a BuildConfig, enter the following command:
This also deletes all builds that were instantiated from this BuildConfig.
To delete a BuildConfig and keep the builds instatiated from the BuildConfig, specify the --cascade=false flag when you enter the following command:

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

This displays information including:

The build source.
The build strategy.
The output destination.
How the build was created.

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

Procedure

To view build details, enter the following command:
```
$ oc describe build <build_name>
```

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

Procedure

To stream the logs using the build directly, enter the following command:
```
$ oc describe build <build_name>
```

Accessing BuildConfig logs

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

Procedure

To stream the logs of the latest build for a , enter the following command:
```
$ oc logs -f bc/<buildconfig_name>
```

Accessing BuildConfig logs for a given version build

You can access logs for a given version build for a BuildConfig using the web console or the CLI.

Procedure

To stream the logs for a given version build for a BuildConfig, enter the following command:
```
$ oc logs --version=<number> bc/<buildconfig_name>
```

You can enable a more verbose output by passing the BUILD_LOGLEVEL environment variable as part of the sourceStrategy or dockerStrategy in a BuildConfig.

Available log levels for source builds are as follows:

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