If you've configured "branches to build" to use a wild card, and if there are changes on those branches compared to the last time they were built, then a bunch of builds will be queued for the changes on those branches.
You might post your git polling log to show what changes it has detected, or the early part of the build log to show the state of the repository. Mark Waite On Mon, Oct 6, 2014 at 9:55 AM, michaelw <[email protected]> wrote: > Hi All... > > Whenever I kick off a build in jenkins it queues up a bunch of builds > claiming that it is doing so because changes are detected. > > I have disabled all polling etc. > > I did have the commit hook on but is also disabled. > > The only change is that we have moved our git repositories to bit > bucket... again no commit hook configured there. > > I have also monitored the logs during a build and I don't see anything > unusual... > > Please can someone help me trouble shoot this. Maybe I can dial up the > logging so that I can work out why jenkins is behaving like this? > > Thanks > > -- > 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/d/optout. > -- Thanks! Mark Waite -- 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/d/optout.
