Pipeline workspace with suffix @script

[Ullrich Hafner]

I’m currently trying to reproduce a bug [1] in a pipeline that reports CheckStyle warnings. Maybe someone with pipeline knowhow has an idea? I don’t see a way to reproduce this:

A pipeline job with the name 'test' seems to check out and place all files in the folder workspace/test@script. However, the checkstyle publisher tries to locate these files in the folder workspace/test (without the @script) suffix. When I look into the workspace folder on my machine I’m finding a folder 'test' with all the files and an empty folder 'test@tmp‘. But there is no folder ’test@script’ on my machine. Are there some circumstances where an @script folder is created? (And a side note: what is placed into the folder @tmp?)

[1] https://issues.jenkins-ci.org/browse/JENKINS-42095?focusedCommentId=291486&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-291486

[Jesse Glick]

On Thu, Apr 27, 2017 at 1:32 PM, Ullrich Hafner
<ullrich...@gmail.com> wrote:
> Are there some circumstances where an @script folder is created?

When you are using `CpsScmFlowDefinition` and are disabling the
recently introduced “lightweight” mode (or it cannot be used for
various reasons).

> what is placed into the folder @tmp?

Anything asking for a temporary folder associated with the workspace.
Durable task control directories, secret files bound via
`withCredentials`, etc., or just anything the user wants to put there
using `pwd tmp: true`.