[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title Jesse Glick commented on JENKINS-39667 Re: PIpeline job ignores custom workspace location Just use the dir or ws steps as needed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176244.1478864055000.18988.1563892081554%40Atlassian.JIRA.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title ASHOK MOHANTY commented on JENKINS-39667 Re: PIpeline job ignores custom workspace location Quick question.. We are using Jenkins 2.121.3 (& planning to upgrade to 2.164.3). Can I use custom workspace in Multibranch/Script pipeline !? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176244.1478864055000.18788.1563885180997%40Atlassian.JIRA.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title 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? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title 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 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title Dmitriy Belyaev updated an issue Jenkins / JENKINS-39667 PIpeline job ignores custom workspace location Change By: Dmitriy Belyaev Labels: pipeline workspace Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title
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
