[RELENG-92] new integration/distribution job that will build final release using managed release and unmanaged projects from staging repos Created: 12/Apr/18 Updated: 12/Apr/18 |
|
| Status: | Open |
| Project: | releng |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Jamo Luhrsen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Managed release tooling |
| Description |
|
Thanh has idea about having projects create their own staging repos, link RelMang team to that as "this is my release, please include it", we aggregate that into a release repo and release it. This set of URLs to staging repos will live in an Int/Dist POM. Int/Dist will build with these, the existing MR distro, produces the final distro. These resulting artifacts would go to Int/Dist's staging repo. Projects would get their artifacts into the staging repos they want to produce using maven-staging job. Not sure if all projects have this, need all of them to. This could replace the merge job. MR staging -> Int/Dist staging -> all unmanaged staging repos |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 12/Apr/18 ] |
|
This is the workflow I'm currently thinking although it will likely change as we start deploying and writing the new jobs and hitting issues: Phase 1: 1. autorelease produces the managed release (same as today, nothing is changed) and produces staged repo Phase 2: 1. autorelease produces the managed release (same as today, nothing is changed) and produces staged repo Release time: 1. each project will contribute to int/dist's pom.xml file containing the staged repos with their final staged repo URL |