Alternatively, you can add an init script to Jenkins :
https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Jenkins+upon+start+up
This script can call "jenkins.model.Jenkins.instance.doQuietDown()" to put
Jenkins in "quiet" mode on startup. Then, you can wait your slaves to
start, and exit quiet
This sounds like you have slaves as well as polling the SCM.
Which is pretty much a bit of a side effect, as the polling will kick off
potentially before the slaves are available - so the last known revision is
not available (its in the workspace) and so a new build is kicked off to
get the rev
In our project we have observed that whenever we restart the jenkins
service, it kicks of all the builds even though builds are configured using
SCM polling.
is this an expected behavior ?
Can someone tell me a solution if it is not an expected behavior ?
Thanks,
Maneesh
--
You received this
