Which command updates the build configuration to set the build log level to 4?

Which command updates the build configuration to set the build log level to 4?

• A. oc start-build <buildconfig_name> --env=<key>=<value>
• B. oc logs -f build jhost-1
• C. oc set env bc/name BUILD_LOGLEVEL=4
• D. oc set triggers bc/name --from-image=project/image:tag

Answer: (C)

Setting the build log level by updating the BuildConfig’s environment is done with a command that stores environment variables on the BuildConfig resource itself. BUILD_LOGLEVEL=4 is an environment variable that the builder recognizes to control how verbose the build logs are. By applying oc set env to the BuildConfig, you persist this setting in the build configuration, so every subsequent build uses log level 4 automatically. This is the right approach when you want the change to apply to all future builds rather than just a single build run. Starting a build with an override (--env) would affect only that one build and not update the configuration. Viewing build logs simply displays output from a build that has already run, and adjusting triggers changes how builds are kicked off, not the log verbosity.

Setting the build log level by updating the BuildConfig’s environment is done with a command that stores environment variables on the BuildConfig resource itself. BUILD_LOGLEVEL=4 is an environment variable that the builder recognizes to control how verbose the build logs are. By applying oc set env to the BuildConfig, you persist this setting in the build configuration, so every subsequent build uses log level 4 automatically. This is the right approach when you want the change to apply to all future builds rather than just a single build run.

Starting a build with an override (--env) would affect only that one build and not update the configuration. Viewing build logs simply displays output from a build that has already run, and adjusting triggers changes how builds are kicked off, not the log verbosity.