Nevermind, I was mixing up a few concepts when taking a look at this. Do the contents of the script directly get stored somewhere during execution for a build? What happens if I make changes to the contents of the script for a build while a previous build is in the middle of execution?
On Tuesday, October 11, 2016 at 11:06:36 AM UTC-5, Jared Kauppila wrote: > > 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/8915b048-122f-4323-83be-0bb37a6573e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
