Which command starts a build with an environment variable KEY=VALUE?

Which command starts a build with an environment variable KEY=VALUE?

• A. oc set env bc/name BUILD_LOGLEVEL=4
• B. oc start-build <buildconfig_name> --env=<key>=<value>
• C. oc patch dc/demo-app --patch '{"spec":{}}'
• D. oc secrets link builder my secret

Answer: (B)

Injecting the variable at build start so it’s visible to the build steps is done with the start-build command and the --env flag. Using oc start-build <buildconfig_name> --env=<key>=<value> launches a new build for that BuildConfig and sets KEY to VALUE inside the build container as it runs. This is the exact way to pass a one-time variable into that specific build. Modifying the BuildConfig with a command like oc set env would affect the default environment for all future builds, not start a single build with a one-off variable. Patching a DeploymentConfig or linking a secret doesn’t start a build or inject build-time environment variables.

Injecting the variable at build start so it’s visible to the build steps is done with the start-build command and the --env flag. Using oc start-build --env== launches a new build for that BuildConfig and sets KEY to VALUE inside the build container as it runs. This is the exact way to pass a one-time variable into that specific build.

Modifying the BuildConfig with a command like oc set env would affect the default environment for all future builds, not start a single build with a one-off variable. Patching a DeploymentConfig or linking a secret doesn’t start a build or inject build-time environment variables.