Description:
Out of scope for #3171 but to prevent duplication of pipeline image building, we'd like to "build only once" and pull that image in the future with a system for tagging and promoting images to next tier.
OFA & UX team: Please include bullets capturing the value to STT end users, related guidance, and/or talking points that should be communicated to STTs in release notes
Acceptance Criteria:Create a list of functional outcomes that must be achieved to complete this issue
[ ] CircleCI Pipeline execution time should be notable faster
[ ] Promotion and tagging system is documented and as intuitive as possible
[ ] Nexus houses docker images
[ ] HHS pipelines should not be inhibited
[ ] Testing Checklist has been run and all tests pass
[ ] README is updated, if necessary
Tasks:Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
[ ] Spike + technical documentation to write a tech memo for operational approach, tagging paradigm, and scripting scope
[ ] Configure Nexus tagging and storage
[ ] Write script(s) to implement promotion and re-use of docker images
[ ] Test for our use-cases: local, features pipeline, develop pipeline, release paths
[ ] [STRETCH] Write test script for use within pipelines
[ ] Run Testing Checklist and confirm all tests pass
Notes:
Supporting Documentation:
Open Questions:
Are there existing systems/libraries we can use for this instead of home-rolling our own which might contain bugs?
How do we deprecate/delete older images?
Can we intuitively associate image identifier with branches and/or releases?
Description: Out of scope for #3171 but to prevent duplication of pipeline image building, we'd like to "build only once" and pull that image in the future with a system for tagging and promoting images to next tier.
OFA & UX team: Please include bullets capturing the value to STT end users, related guidance, and/or talking points that should be communicated to STTs in release notes
Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
Notes:
Supporting Documentation:
Open Questions: