Configure Nexus 3' staging repositories
(BUILD-699)
|
|
| Status: | Completed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Team: |
| Description |
|
Nexus 3 staging no longer works with creating staging repos on the fly, but based on tagging & permanent staging repos. Promotion happens by moving artifacts with a certain tag to a target destination repository. Possible approachesIn theory, one shared staging repo would be sufficient, if we (or automation) keep track of which tag goes where. However, if promotion is a deferred step, and one inspects the content of that unique repo, it might be messy to identify e.g. if all community artifacts have been promoted, or which hanging artifacts need to be promoted where. Therefore, in order to be able to promote public, enterprise and other artifacts to their correct destination repos, it's gonna be more "magnolia-conventional" to have:
Same for following repos/”scopes”:
Repos not using staging at this point:
Validation points 🧪
—via Nexus aftermath and Foundation impact @August 8, 2023 |