-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.10.1
In a pipeline scm checkout, when using non-lightweight checkout, and the global setting "SCM checkout retry count" is a non-zero value, if a build is performing the initial scm clone and the build is cancelled, the retry will relaunch the scm step as per the retry count. I believe this is contrary to the pipeline retry step which will not retry if a build is cancelled.
Found this
https://issues.jenkins-ci.org/browse/JENKINS-39194
and
https://github.com/jenkinsci/workflow-cps-plugin/pull/147
In our use-case we integrate with Gerrit, with the same setup
Using non-lightweight checkout, and the global setting "SCM checkout retry count" is '4'. If a new patchset is pushed to Gerrit while the current patchset is performing the scm clone, that clone gets killed, but because of the gloabl retry another clone in the old build starts and the pipeline build proceeds with the entire build. The old build should abort and terminate.