Create base images and tag them for `build.next` and `build.current` Golang builder images
Final Outcome
Using the same version track and updates as Omnibus GitLab because tracking the changes against CNG before we optimize that workflow would be too much for the first iteration.
- registry.gitlab.com/gitlab-org/distribution/build-compliance/release-frameworks/framework_go_amd64:current
- registry.gitlab.com/gitlab-org/distribution/build-compliance/release-frameworks/framework_go_amd64:next
- registry.gitlab.com/gitlab-org/distribution/build-compliance/release-frameworks/framework_go_arm64:current
- registry.gitlab.com/gitlab-org/distribution/build-compliance/release-frameworks/framework_go_arm64:next
Overview
We need to create the two build images and tags that will allow other teams to build their Go based projects as needed.
Considerations
Distribution team is working on efficiency. One of the long term goals is the elimination of double builds so that CNG and Omnibus are using the exact same built artifacts. Spike: Idea to Parallelize Omnibus Building and... (#596 - closed) is the first step in that longer term goal.
Deliverables
Identify which container base currently used to build our shipping product should be the base image:
Edited by Robert Marshall