[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location

4uva4ok@gmail.com (JIRA)

unread,

Nov 11, 2016, 6:35:02 AM11/11/16

to jenkinsc...@googlegroups.com

Dmitriy Belyaev created an issue

Jenkins /

JENKINS-39667

PIpeline job ignores custom workspace location

Issue Type:	Bug
Assignee:	Unassigned
Components:	pipeline
Created:	2016/Nov/11 11:34 AM
Environment:	Windows 7, x64 Jenkins 2.19.2 Pipeline 2.4
Priority:	Major
Reporter:	Dmitriy Belyaev

After last update (not sure which one, everything worked last time on 4. nov 2016) pipeline job began to use local jenkins directory (c:/Users/jenkins/.jenkins) for workspaces completely ignoring settings set under: "Manage Jenkins / Worspace Root DIrectory" and "Manage Jenkins / Build Record Root Directory", which are configured as follow:

Workspace Root Directory = d:/jenkins/ws/$

{ITEM_FULLNAME}/work
Build Record Root Directory = d:/jenkins/ws/${ITEM_FULLNAME}

/builds

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

4uva4ok@gmail.com (JIRA)

unread,

Nov 16, 2016, 9:24:01 AM11/16/16

to jenkinsc...@googlegroups.com

Dmitriy Belyaev updated an issue

Jenkins /

JENKINS-39667

PIpeline job ignores custom workspace location

Change By:	Dmitriy Belyaev
Labels:	pipeline workspace

Add Comment

jglick@cloudbees.com (JIRA)

unread,

Dec 5, 2016, 5:37:02 PM12/5/16

to jenkinsc...@googlegroups.com

Jesse Glick resolved as Won't Fix

If you are referring to multibranch Pipeline jobs (branch projects), this is intentional; see release notes for workflow-multibranch.

Jenkins /

JENKINS-39667

PIpeline job ignores custom workspace location

Change By:	Jesse Glick
Status:	Open Resolved
Resolution:	Won't Fix

Add Comment

4uva4ok@gmail.com (JIRA)

unread,

Dec 6, 2016, 4:18:01 AM12/6/16

to jenkinsc...@googlegroups.com

Dmitriy Belyaev commented on

JENKINS-39667

Re: PIpeline job ignores custom workspace location

Jesse Glick I do understand that it will take some time for your to find a correct link, but referring to release note of workflow-multibranch plugin without any details does not help a lot. By reading latest changelog on the above named plugin I could not find any mention of workspace handling changes (changelog: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin).

Add Comment

micheljung@java.net (JIRA)

unread,

Mar 31, 2017, 10:50:01 AM3/31/17

to jenkinsc...@googlegroups.com

micheljung commented on

JENKINS-39667

Re: PIpeline job ignores custom workspace location

I don't understand how "this is intentional" is a justification for this unexpected and very problematic behavior. Unfortunately I'm not able to find anything in the release notes either.

Our project can't even be cloned because of this, making it impossible to use pipeline builds. And even if it wasn't problematic because of the path length:

"As builds tend to be disk I/O intensive, changing this value enables you to put build workspaces on faster storage hardware, such as SSDs or even RAM disks."

We don't get this with pipeline builds?

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

micheljung@java.net (JIRA)

unread,

Mar 31, 2017, 11:01:01 AM3/31/17

to jenkinsc...@googlegroups.com

micheljung edited a comment on

JENKINS-39667

Re: PIpeline job ignores custom workspace location

I don't understand how "this is intentional" is a justification for this unexpected and very problematic behavior. Unfortunately , I'm not able to find anything any explanation in the release notes either.

Our project can't even be cloned because of this, making it impossible to use pipeline builds. And even if it wasn't problematic because of the path length:

"As builds tend to be disk I/O intensive, changing this value enables you to put build workspaces on faster storage hardware, such as SSDs or even RAM disks."

We don't get this with pipeline builds?