Value Statement

Can the common build pipeline apply common labels that all of our images need to define?

During ACM 2.16, teams had to define the name and cpe labels.   There are other labels we need to override which the base image current provides today - example is the url label.

Definition of Done for Engineering Story Owner (Checklist)

• A defined procedure to apply a label to every image that is built using the common pipeline definitions.
• How do component specific details get added to the label, such as for the url?

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.