-
Bug
-
Resolution: Fixed
-
Major
-
None
When pulling my workflow script from a svn repo I get two builds triggered for one revision change if build runs longer then pull interval,
To reproduce:
Create workflow job with a standard svn pull configured in job, for my test I set to every minute
Sample Job DSL
---------------------------------------
node ('master') { checkout changelog: false, poll: false, scm: [ $class: "SubversionSCM", locations: [[ remote:'SVNURL/trunk/flow']] ] load 'flow/Test.groovy' }()
Sample Test.groovy
---------------------------
{ -> node() { ws() { checkout changelog: true, poll: true, scm: [$class: "SubversionSCM", locations: [[remote: 'SVNURL/trunk']]] sleep 300 } } }
Note: I pull my workflow scripts from the same repo as my build.
Any scheduled poll that happens before build completion will trigger another job,
Looking at the polling log it seems it is comparing against the last completed build and not the in progress.
Notes:
- https://subversion.assembla.com/svn/evildethow-svn/trunk can be used to test this
- This triggered 6 builds for me
- Disabling concurrent builds dropped it to 2
- MultipleSCM is being used
- is duplicated by
-
JENKINS-30871 Workflows are executed multiple times if they take longer than their poll period
- Resolved
- relates to
-
JENKINS-40255 WorkflowJob.getSCMs() should have similar behaviour as poll()
- Resolved
- links to