Which command configures a post-commit build hook to run a script ("curl http://api.com/user/${USER}") for a BuildConfig named "name"?

Which command configures a post-commit build hook to run a script ("curl http://api.com/user/${USER}") for a BuildConfig named "name"?

• A. oc set build-hook bc/name --post-commit --command -- curl http://api.com/user/${USER}
• B. oc set build-hook bc/name --post-commit --command bundle exec rake test --verbose
• C. oc set build-hook bc/name --post-commit --script="curl http://api.com/user/${USER}"
• D. oc set build-hook bc/name --pre-commit --script="curl http://api.com/user/${USER}"

Answer: (C)

Setting up a post-commit hook to run a script in OpenShift is done by attaching a script to the BuildConfig’s post-commit hook using oc set build-hook, targeting the BuildConfig by bc/name and providing the script as a single string. The correct form uses the post-commit flag and the script option, with the curl command placed inside quotes so it’s executed as one script piece after the commit finishes. The ${USER} variable will be expanded by the shell when the script runs, sending the appropriate user value to the API. So, using --post-commit with --script="curl http://api.com/user/${USER}" is the proper syntax, and it ensures the hook fires after the commit and runs exactly that command. The other approaches either target a different hook (pre-commit), or misuse the command format (such as not quoting the script or using an option form that isn’t intended for a script), which would not achieve the required post-commit behavior.

Setting up a post-commit hook to run a script in OpenShift is done by attaching a script to the BuildConfig’s post-commit hook using oc set build-hook, targeting the BuildConfig by bc/name and providing the script as a single string. The correct form uses the post-commit flag and the script option, with the curl command placed inside quotes so it’s executed as one script piece after the commit finishes. The ${USER} variable will be expanded by the shell when the script runs, sending the appropriate user value to the API.

So, using --post-commit with --script="curl http://api.com/user/${USER}" is the proper syntax, and it ensures the hook fires after the commit and runs exactly that command. The other approaches either target a different hook (pre-commit), or misuse the command format (such as not quoting the script or using an option form that isn’t intended for a script), which would not achieve the required post-commit behavior.