I am observing the same behavior, and makes any version of Jenkins above 1.480 unusable for us. An job listed as an upstream dependency will kick off about 50+ builds upon completion, even though there is no actual dependency between the projects.
Is this a known issue? Or am I missing some way of configuring this behavior? ~ kc On Tuesday, September 18, 2012 9:41:51 AM UTC-7, Jack Haughton wrote: > > Hello, > > After recently upgrading to Jenkins 1.482 from 1.37x (don't have exact > version to hand), we found that all the 'upstream/downstream dependencies' > sections in our Maven builds were pointing to different branches. We have a > lot of similar featurebranched builds, with names of the form "<group id> > <artifact id> <branch name>'. The effect of this issue was that all the > dependencies pointed to one particular branch, instead of pointing to the > same branch as the job they were on. The artifacts were still correct, it > was just the branch (which we represent as the Maven version) which was > incorrect. > > I take it this is something to do with the maven versioning change in > 1.481? > > Thanks > Jack >
