Which command adds an image trigger to a build configuration from a specific image tag?

Which command adds an image trigger to a build configuration from a specific image tag?

• A. oc set triggers bc/name --from-image=project/image:tag
• B. oc set env bc/name BUILD_LOGLEVEL=4
• C. oc secrets link builder my secret
• D. oc patch dc/demo-app --patch '{"spec":{"template":{"spec":{"serviceAccountName":"myserviceaccount"}}}}'

Answer: (A)

Adding an image change trigger to a BuildConfig so builds start automatically when a referenced image tag updates is what this command does. Running oc set triggers bc/name --from-image=project/image:tag attaches an image change trigger to the BuildConfig named name that watches the image stream tag project/image:tag. When a new image is pushed for that tag, OpenShift detects the change and automatically initiates a new build for the BuildConfig. This is different from changing environment variables (which only alters build behavior), linking a secret to the builder (which provides credentials, not triggering), or patching a DeploymentConfig for a service account (which affects deployment, not build triggering).

Adding an image change trigger to a BuildConfig so builds start automatically when a referenced image tag updates is what this command does. Running oc set triggers bc/name --from-image=project/image:tag attaches an image change trigger to the BuildConfig named name that watches the image stream tag project/image:tag. When a new image is pushed for that tag, OpenShift detects the change and automatically initiates a new build for the BuildConfig. This is different from changing environment variables (which only alters build behavior), linking a secret to the builder (which provides credentials, not triggering), or patching a DeploymentConfig for a service account (which affects deployment, not build triggering).