How do you configure OpenShift to trigger a build when a commit is pushed to the Git repository?

How do you configure OpenShift to trigger a build when a commit is pushed to the Git repository?

• A. Manually start builds from CLI
• B. Remove build triggers from BuildConfig
• C. Use a periodic cron job to check source change
• D. Add a webhook trigger to the BuildConfig or enable a Git webhook

Answer: (D)

OpenShift automates builds in response to changes in your source repository by using a webhook trigger on the BuildConfig. This means you set up a Git webhook for the BuildConfig, which gives OpenShift a specific URL to receive a push event from your Git hosting service. When you push a commit, the webhook notifies OpenShift, which validates the request and starts a new build using the configuration in the BuildConfig. Configure this by enabling a Git webhook trigger in the BuildConfig (often with a shared secret for security). Then add the webhook URL to your Git provider’s webhook settings so pushes fire the event automatically. Without this webhook, pushing code won’t start a build unless you intervene manually. Other options don’t provide automatic, real-time reactions to code changes: starting builds manually requires user action each time, removing triggers disables automatic builds, and a periodic cron job would polling for changes rather than responding to the actual VCS event. The webhook approach is the standard, reliable way to trigger builds on commit.

OpenShift automates builds in response to changes in your source repository by using a webhook trigger on the BuildConfig. This means you set up a Git webhook for the BuildConfig, which gives OpenShift a specific URL to receive a push event from your Git hosting service. When you push a commit, the webhook notifies OpenShift, which validates the request and starts a new build using the configuration in the BuildConfig.

Configure this by enabling a Git webhook trigger in the BuildConfig (often with a shared secret for security). Then add the webhook URL to your Git provider’s webhook settings so pushes fire the event automatically. Without this webhook, pushing code won’t start a build unless you intervene manually.

Other options don’t provide automatic, real-time reactions to code changes: starting builds manually requires user action each time, removing triggers disables automatic builds, and a periodic cron job would polling for changes rather than responding to the actual VCS event. The webhook approach is the standard, reliable way to trigger builds on commit.