-
Notifications
You must be signed in to change notification settings - Fork 8
Brain Dump 1
Andrei Pozolotin edited this page Mar 3, 2013
·
1 revision
To release a given artifact, some things that need to happen:
- For each direct dependency having a "SNAPSHOT" version.
- Find the associated Jenkins Job matching Maven coordinates {groupId:artifactId:version}
- If no job exists - Halt process
- else recursively build list of jobs
- Multi-tier
- Top Tier : top-level project being released
- 2nd Tier : Direct Dependencies
- 3rd Tier : First level transitive dependencies
- ...
- Nth Tier : Nth level transitive dependencies.
- Reactor standard Maven release process for artifacts starting at Nth Tier, then working up to Top Tier
- Top Tier may be the only tier that requires new cascading release functionality
- Trigger Jenkins Jobs for releases instead of simply invoking the maven command in the workspace.
- ?? Should it wait for Tier N to complete before releasing Tier N-1 ??
- I think it has to, so that tier N-1 can be updated with Tier N's newly released version - @jjongsma
- How to query Jenkins for a list of jobs with Maven coordinate information?
- How to programmatically trigger the Jenkins "M2 Release Plugin" for dependencies?