Hi. After we added many more integration tests to our project the build now runs about 20 minutes instead of 10 before. This causes jenkins to always run 2 builds for 1 SCM change, because the build is still running when SCM poll next time in his interval.
In Detail: Scenario: SCM polling interval is smaller than build duration. e.g. polling intervall 15min, build duration about 20 min My observations are: Build #1 Started on 14.10.2013 18:30:50 Using locally configured password for connection to :pserver:jenkins@... cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:30:50 +0200 my_project Done. Took 1,6 Sekunden Changes found This is ok, there are changes which are also shown in the changeset, build is started and will go until [INFO] Total time: 20 minutes 25 seconds [INFO] Finished at: Mon Oct 14 18:51:50 CEST 2013 [INFO] Final Memory: 90M/220M Now what about the next build? Build #2 Started on 14.10.2013 18:45:50 Using locally configured password for connection to :pserver:jenkins@... cvs rlog -S -d14 Oct 2013 18:06:57 +0200<14 Oct 2013 18:45:50 +0200 my_project Done. Took 1,5 Sekunden Changes found As you can see, the CVS poll is done exactly in the configured polling intervall, 15min later. So far ok. But the cvs command uses the timestamp "Oct 2013 18:06:57" which is the same as for build#1. I think this causes the second poll to find the same changes as the first poll. The real build then starts later, one second after the first build is finished: Build wurde durch eine SCM-Änderung ausgelöst. Baue auf Slave prod01 in workspace /var/jenkins/workspace/my_project Using locally configured password for connection to :pserver:jenkins@... cvs checkout -P -D 14 Oct 2013 18:51:53 +0200 -d MZV-Online Sportdatenbank my_project Using locally configured password for connection to :pserver:jenkins@... cvs rlog -S -d14 Oct 2013 18:30:52 +0200<14 Oct 2013 18:51:51 +0200 my_project At the start of the build, SCM is polled again, but not with the newer timestamp "Oct 2013 18:30:52" to get only changes after the scm poll of the first build. The result is, that for the second build it says a) Build was triggered by scm changes and b) no changes So in the end, we always get two builds for each SCM change. I think this could be fixed, if the initial SCM poll of the second build uses the timestamp "Oct 2013 18:30:52" and not "Oct 2013 18:06:57" But I don't know how to change this behaviour. Would be nice to get any help. Bye, Horst -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
