7.5. Accessing build logs

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>
```
```
$ oc describe build <build_name>
```
Copy to Clipboard Toggle word wrap

7.5.1. 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 BuildConfig, enter the following command:
```
oc logs -f bc/<buildconfig_name>
```
```
$ oc logs -f bc/<buildconfig_name>
```
Copy to Clipboard Toggle word wrap

7.5.2. 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>
```
```
$ oc logs --version=<number> bc/<buildconfig_name>
```
Copy to Clipboard Toggle word wrap

7.5.3. Enabling log verbosity
复制链接

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

注意

An administrator can set the default build verbosity for the entire OpenShift Container Platform instance by configuring env/BUILD_LOGLEVEL. This default can be overridden by specifying BUILD_LOGLEVEL in a given BuildConfig. You can specify a higher priority override on the command line for non-binary builds by passing --build-loglevel to oc start-build.

Available log levels for source builds are as follows:

Level 0	Produces output from containers running the `assemble` script and all encountered errors. This is the default.
Level 1	Produces basic information about the executed process.
Level 2	Produces very detailed information about the executed process.
Level 3	Produces very detailed information about the executed process, and a listing of the archive contents.
Level 4	Currently produces the same information as level 3.
Level 5	Produces everything mentioned on previous levels and additionally provides docker push messages.

Procedure

To enable more verbose output, pass the BUILD_LOGLEVEL environment variable as part of the sourceStrategy or dockerStrategy in a BuildConfig:
```
sourceStrategy:
...
  env:
    - name: "BUILD_LOGLEVEL"
      value: "2" 
```
```
sourceStrategy:
...
  env:
    - name: "BUILD_LOGLEVEL"
      value: "2" 
```
1
Copy to Clipboard Toggle word wrap
1
Adjust this value to the desired log level.

返回顶部

7.5. Accessing build logs

7.5.1. Accessing BuildConfig logs
复制链接

7.5.2. Accessing BuildConfig logs for a given version build
复制链接

7.5.3. Enabling log verbosity
复制链接

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

7.5. Accessing build logs

7.5.1. Accessing BuildConfig logs复制链接链接已复制到粘贴板!

7.5.2. Accessing BuildConfig logs for a given version build复制链接链接已复制到粘贴板!

7.5.3. Enabling log verbosity复制链接链接已复制到粘贴板!

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

7.5.1. Accessing BuildConfig logs
复制链接

7.5.2. Accessing BuildConfig logs for a given version build
复制链接

7.5.3. Enabling log verbosity
复制链接