More importantly, what is the best way of cleaning up the @script folders?
On Thursday, August 4, 2016 at 2:37:09 PM UTC-4, jer...@bodycad.com wrote:
>
> Just realized the same thing, after developing my JenkinsFile inline with
> sandbox removed, then approved the whole operation into white listi
Just realized the same thing, after developing my JenkinsFile inline with
sandbox removed, then approved the whole operation into white listing. That
@script folder was unexpected for the least I could say
On Monday, August 1, 2016 at 7:30:04 PM UTC-4, Peter Wiseman wrote:
>
> Likewise, I'm conc
Likewise, I'm concerned about a full checkout into workspace@script. Seems
to be overkill if it's just to find the Jenkinsfile. With multiple active
branches (each 3GB), that's seemingly quite a lot of unnecessary permanent
storage.
--
You received this message because you are subscribed to
Interesting. We have not got to using the Jenkinsfile "discovery"
functionality yet, but this is good to know. I'll keep my eyes open for
more on this subdirectory.
On Friday, April 1, 2016 at 12:49:46 PM UTC-7, tomwils...@gmail.com wrote:
>
> Thank you Brian, you're right regarding the @tm
Thank you Brian, you're right regarding the @tmp directory. However
the @script directory seems to be different.
I'm searching in the source code of the workflow cps plugin. The file
CpsScmFlowDefinition.java seems to be the place where the workspace@script
behavior is implemented.
https://issues.jenkins-ci.org/browse/JENKINS-27152
I'm not sure about @script but suspect it's a similar necessity.
On Friday, April 1, 2016 at 12:00:18 AM UTC-7, tomwils...@gmail.com wrote:
>
> Hello,
>I'm trying to setup Jenkins to run a multibranch pipeline project.
> Just to test, I use
Hello,
I'm trying to setup Jenkins to run a multibranch pipeline project. Just
to test, I use a very simple Jenkinsfile like this:
node {
checkout scm
bat 'echo > tst1.txt'
}
When I run the build, for each branch, for example the 'master' branch,
Jenkins creates 3 directories:
- workspace@s
