Epic Goal

• Improve the nightly build automation to be more transparent in its inputs and outputs
• Build pipelines declare their build results as build artifacts for ease of location
• Images are labeled with their upstream and downstream revisions and when possible their version
• Automated updates and nudges link back to their triggering action for auditability
• Konflux's infra-deployments CI detects changes to to the pipelines index and compares the diff in a comment
• Tooling is developed to generate release notes between two indexes

Why is this important?

• CCE team members have to interact with nightly builds and must be able to gain information on the build contents from the build itself rather than finding the build given the contents.

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Nightly build procedures are documented in Confluence in the form of SOPs

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment