Re: Pipeline checkout persistence issue

2018-10-17 Thread Andrew Bayer
I'd advise moving the checkout logic into a shared library, fwiw. A. On Wed, Oct 17, 2018 at 2:00 PM James Chapman wrote: > Yeah, the default checkout is definitely the problem, even though it's > "lightweight", it isn't. When I then perform a chekout step, once complete > the default checkout

Re: Pipeline checkout persistence issue

2018-10-17 Thread James Chapman
Yeah, the default checkout is definitely the problem, even though it's "lightweight", it isn't. When I then perform a chekout step, once complete the default checkout reverts the directory and it then becomes "lightweight", so only the Jenkinsfiles remain and the source I'm trying to build evaporat

Re: Pipeline checkout persistence issue

2018-10-17 Thread Andrew Bayer
You might want to add "skipDefaultCheckout(true)" to your options - it could be that the automatic checkout that happens whenever you enter an agent is messing things up. A. On Wed, Oct 17, 2018 at 11:40 AM James Chapman wrote: > Hello Jenkins users, > > I have a pipeline job that run across a

Pipeline checkout persistence issue

2018-10-17 Thread James Chapman
Hello Jenkins users, I have a pipeline job that run across a whole lot of different platforms. The job checks out source code on each node, builds on each node, runs tests on each node and then completes. Pretty straightforward! For some reason, when the checkout finishes, all the files that were