Goal:

Support ImageChange triggers for BuildConfigs when used in GitOps deployments.

Problem:

ImageChange triggers record the last image that triggered the build in the BuildConfig's spec. This is problematic for GitOps frameworks, which reconcile the status of object specs stored in git with those on a cluster.

Why is this important?

GitOps is an advocated method for teams to manage their OpenShift deployments

Dependencies

• BUILD-189 - Deprecate LastImageChangeTriggeredID

Stories and Deliverables

• BUILD-188 - Only use status to trigger builds

Estimate: (XS, S, M, L, XL, XXL) S

Previous Work:

• BUILD-189
• https://bugzilla.redhat.com/show_bug.cgi?id=1876500

User Stories:

As a developer using OpenShift for builds
I want ImageChanges to trigger builds based on information recorded in the BuildConfig status
So that I can use ImageChange triggers with builds in a GitOps workflow

Success Criteria:

• `oc apply -f` on a BuildConfig YAML manifest with ImageChange triggers will only trigger a build if the referenced base image has been updated.

Open Questions:

See https://docs.google.com/document/d/1thcVR31TElJBXBGmyaYXZ9jRejp5W4-ppNYn4g3_mgk/edit# for a fuller explanation on how to use this template.