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