I think this should get fixed or reverted and back ported into the new LTS
release.
/Domi
On 18.10.2012, at 21:43, Jeff Maxwell jeff.maxw...@gmail.com wrote:
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
Thanks for linking to the Jira Issue I created a few days ago. This
traffic should raise some attention. It's an annoying problem for us that
puts our build validity at risk. The Maven-Jenkins integration is a great
feature for us.
https://issues.jenkins-ci.org/browse/JENKINS-15367
Kohsuke
I got kohsuke's attention on IRC, and directed him to this thread and the
ticket in question. This is also affecting the maven developers with their
git migration:
http://maven.40175.n5.nabble.com/Jenkins-jobs-for-the-projects-that-have-migrated-to-git-td5724895.html
-- Larry
On Mon, Oct 15,
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
+1 too
On 24.09.2012, at 22:42, Arnaud Héritier aherit...@gmail.com wrote:
Hi,
+1000 with Larry
I also noticed this issue triggering many many useless builds between
projects.
I was also suspecting this change as the root cause of the issue.
Is there already an issue opened
+1
2012/9/24 Arnaud Héritier aherit...@gmail.com:
Hi,
+1000 with Larry
I also noticed this issue triggering many many useless builds between
projects.
I was also suspecting this change as the root cause of the issue.
Is there already an issue opened about this regression ?
I'm
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
