Any thoughts on this? I haven't been able to find a workaround. Since we're using the JenkinsFile that path, we are unable to run concurrent jobs.
On Wednesday, August 10, 2016 at 12:50:42 PM UTC-5, Jared Kauppila wrote: > > Hello, > > We are currently running Jenkins 2.7.2 and have a pipeline job defined > that utilizes the 'Pipeline script from SCM' SVN repo at the very start, as > a result, we get the following folders upon execution: > > > - Dev_Pipeline > - Dev_Pipeline@script > - Dev_Pipeline@tmp > > When we kick off another concurrent build, we get the following additional > folders: > > > > - Dev_Pipeline@2 > - Dev_Pipeline@2@tmp > > Is there any particular reason it's not pulling down the SVN repo into a > 'Dev_Pipeline@2@script' as well? I can't find a configuration option to > allow this. > > > Thanks, > > Jared > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f17764d4-ff16-430c-8f0d-a2bc95645c83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
