Re: Does 'scm checkout' always give the same result with parallel builds in JenkinsFiles ?

It was released as part of git plugin versions git-3.1.0, git-3.0.5, git-3.0.4, git-3.0.3, git-3.0.2, git-3.0.1, git-2.6.5, git-2.6.4, git-2.6.2, and git-2.6.1. Mark Waite On Sun, Mar 19, 2017 at 2:07 AM wrote: > Was this merged already? > Is it safe to use checkout

Re: Does 'scm checkout' always give the same result with parallel builds in JenkinsFiles ?

Was this merged already? Is it safe to use checkout scm within for parallel jobs? On Thursday, September 22, 2016 at 6:53:06 AM UTC+3, Mark Waite wrote: > > The intent of the checkout scm step is that it takes a single revision, > and uses that revision for the duration of the job. > >

Re: Does 'scm checkout' always give the same result with parallel builds in JenkinsFiles ?

Thanks for the quick reply. Any info about the recommended way to get the sha that was actually used ? -- 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

Re: Does 'scm checkout' always give the same result with parallel builds in JenkinsFiles ?

The intent of the checkout scm step is that it takes a single revision, and uses that revision for the duration of the job. Unfortunately, a bug was found during discussions after Jenkins World which seem to indicate that there area cases where git plugin 2.5.3 and beyond risks not checking out

Does 'scm checkout' always give the same result with parallel builds in JenkinsFiles ?

Hi I was playing with JenkinsFiles and Organization folders (multi-branch pipeline) and I was wondering: Is there is any guarantee the 'checkout scm' command would checkout the exact same revision on all node, even if new commits are pushed before the build is finished ? Also, I saw an