We have the same requirement.
On Thursday, September 27, 2012 11:02:00 AM UTC-5, liam.j.bennett wrote: > > While this is clearly a bug that needs fixing it would be useful to have > the functionality to resolve downstream/upstream jobs with a fixed version > (configurable of-course). > > We no longer use SNAPSHOTS but use release versions with > BUILD_ID-BUILD_NUMBER and dynamically update dependencies using the > maven-versions-plugin at build time. At the moment we are having to > manually configure downstream/upstream relationships so having Jenkins > auto-resolve them for fixed versions would be very useful to us. > > On Wednesday, September 19, 2012 4:04:37 PM UTC+1, Larry Shatzer, Jr. > wrote: >> >> I've noticed something weird with Maven projects that are set to build >> downstream jobs if there is a SNAPSHOT dependency. It now lists jobs as >> dependencies (and builds them) even if it is not a SNAPSHOT dependency but >> a regular dependency. >> >> It looks like the code for JENKINS-12735 to allow version ranges is >> causing this. If you use version of <version>1.0.0</version>, that should >> not trigger it, but the other uses like [1.0.0,2.0.0), etc. should. This is >> causing lots of extra unnecessary builds when you have a lot of projects >> that are dependent on each other, but set to a release of the other and not >> a SNAPSHOT. >> >> -- Larry >> >
