Hi, I have the same issue. This is more or less my structure: proj-parent --proj-a --proj-b --proj-c I set up a job using the incremental build on Jenkins and if something is committed only to proj-c then only this module is build. But if the same change comes from a reintegrated branch then the whole project is built because the mergeinfo on the root folder are seen as a change on the proj-parent and then all its 3 modules are triggered. According to JENKINS-14685<https://issues.jenkins-ci.org/browse/JENKINS-14685>this should have been fixed in the plugin version 1.44 and I am currently using 1.50. Then Jenkins version I am using is 1.466.2.
Any ideas? Davide On Tuesday, June 5, 2012 10:35:21 PM UTC+2, pgweiss wrote: > > Is there any way to tell a Jenkins project to ignore changes that are > svn:mergeinfo only? The use case is when you have a tree structure > such as: > > projects/ > project-a > project-b > > and someone does an svn merge into projects that only modifies > project-a. If project-b has existing svn:mergeinfo it will be > modified, causing an apparent change to project-b, even though no code > has changed. So Jenkins will schedule a build for any job that depends > on project-b. > > -P > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
