What feature allows a BuildConfig to automatically start a new build when a change is pushed to the connected Git repository?

What feature allows a BuildConfig to automatically start a new build when a change is pushed to the connected Git repository?

• A. Git polling
• B. Auto-commit trigger
• C. BuildConfig triggers
• D. Webhook trigger

Answer: (D)

Webhook triggers are the mechanism that starts a new build automatically as soon as a push happens in the connected Git repository. In OpenShift, you configure a webhook trigger in a BuildConfig and connect it to your Git hosting service. When you push code, the hosting service sends a POST request to the webhook URL with a shared secret, OpenShift validates it, and that event kicks off a new build from the BuildConfig. This approach provides immediate, event-driven builds rather than periodically polling the repository. While BuildConfig supports various triggers, the one that responds to Git pushes is the webhook trigger.

Webhook triggers are the mechanism that starts a new build automatically as soon as a push happens in the connected Git repository. In OpenShift, you configure a webhook trigger in a BuildConfig and connect it to your Git hosting service. When you push code, the hosting service sends a POST request to the webhook URL with a shared secret, OpenShift validates it, and that event kicks off a new build from the BuildConfig. This approach provides immediate, event-driven builds rather than periodically polling the repository. While BuildConfig supports various triggers, the one that responds to Git pushes is the webhook trigger.