[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs

Change By:	James Dumay
Summary:	Support workspaces in for Pipeline jobs

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

aheritier@apache.org (JIRA)

unread,

Nov 21, 2016, 5:01:02 AM11/21/16

to jenkinsc...@googlegroups.com

Arnaud Héritier commented on

Also it may be useful to ease the access to a build/job workspaces. Having to navigate in pipeline steps to find workspaces isn't user friendly. Maybe we could:

1) have a workspace icon (and link) nearby the console icon where relevant on steps view.
2) have a "Workspaces" link on the pipeline job page that opens a "pop up layer" (just as logs does) listing all the workspace links used in the last pipeline build, just as the workspace link of a "standard job" shows the content of the workspace of the last job link.

jglick@cloudbees.com (JIRA)

unread,

Dec 5, 2016, 5:36:10 PM12/5/16

to jenkinsc...@googlegroups.com

Jesse Glick updated an issue

Jenkins /

Change By:	Jesse Glick
Component/s:	workflow-durable-task-step-plugin
Component/s:	workflow-support-plugin

tarazansafak@gmail.com (JIRA)

unread,

Feb 2, 2017, 8:05:04 AM2/2/17

to jenkinsc...@googlegroups.com

safak tarazan commented on

check this out https://www.selikoff.net/2016/07/10/workspace-jenkins-pipelines/

nrovland@yahoo.fr (JIRA)

unread,

Feb 12, 2017, 2:07:02 PM2/12/17

to jenkinsc...@googlegroups.com

Rovland NSANA KISSITA commented on

Thanks guys for tracking this issue , please keep us informed

nrovland@yahoo.fr (JIRA)

unread,

Feb 12, 2017, 2:09:02 PM2/12/17

to jenkinsc...@googlegroups.com

Rovland NSANA KISSITA edited a comment on

Thanks guys for tracking this issue , please keep us informed

[~tarzain] great , thanks for sharing us this tip :)

mneale@cloudbees.com (JIRA)

unread,

Feb 15, 2017, 10:58:03 PM2/15/17

to jenkinsc...@googlegroups.com

Michael Neale assigned an issue to Michael Neale

Jenkins /

Change By:	Michael Neale
Assignee:	Jesse Glick Michael Neale

bgkbharath@gmail.com (JIRA)

unread,

Feb 12, 2018, 12:16:04 AM2/12/18

to jenkinsc...@googlegroups.com

bharath ganesh kumar balasubrmanian commented on

For all those who're particular to look the workspace of multi branch pipeline jenkins projects, please navigate to the build run and click “pipeline steps”, then click “allocate node: start” ( for multiple nodes, this shall be done as required) Tadaaa..!!! you've your workspace button in the left

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

andrew.paul.gray@gmail.com (JIRA)

unread,

Apr 23, 2018, 12:47:05 AM4/23/18

to jenkinsc...@googlegroups.com

Andrew Gray commented on

Yes bharath ganesh kumar balasubrmanian, but where is the Wipe Out Workspace button?

o.v.nenashev@gmail.com (JIRA)

unread,

Aug 7, 2018, 10:01:18 AM8/7/18

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

https://github.com/jenkinsci/external-workspace-manager-plugin actually supports browsing of workspaces for Pipeline, but it requires extra configuration

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

jglick@cloudbees.com (JIRA)

unread,

Aug 7, 2018, 10:14:10 AM8/7/18

to jenkinsc...@googlegroups.com

Jesse Glick commented on

Oleg Nenashev that is unrelated. This issue is just about exposing a proper UI for workspace access in Pipeline builds, without changing runtime behavior.

o.v.nenashev@gmail.com (JIRA)

unread,

Aug 7, 2018, 10:19:03 AM8/7/18

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

I understand. This is just one of possible workarounds if the feature is really needed

jglick@cloudbees.com (JIRA)

unread,

Sep 21, 2018, 12:34:16 PM9/21/18

to jenkinsc...@googlegroups.com

Jesse Glick assigned an issue to Jesse Glick

Jenkins /

Change By:	Jesse Glick
Assignee:	Jesse Glick

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jglick@cloudbees.com (JIRA)

unread,

Sep 21, 2018, 12:34:17 PM9/21/18

to jenkinsc...@googlegroups.com

Jesse Glick started work on

Change By:	Jesse Glick
Status:	Open In Progress

jglick@cloudbees.com (JIRA)

unread,

Sep 21, 2018, 12:34:30 PM9/21/18

to jenkinsc...@googlegroups.com

Jesse Glick updated an issue

Jenkins /

Change By:	Jesse Glick
Component/s:	workflow-support-plugin
Component/s:	workflow-durable-task-step-plugin

jglick@cloudbees.com (JIRA)

unread,

Sep 21, 2018, 1:13:16 PM9/21/18

to jenkinsc...@googlegroups.com

Jesse Glick updated

Jenkins /

Change By:	Jesse Glick
Status:	In Progress Review

jglick@cloudbees.com (JIRA)

unread,

Sep 21, 2018, 1:13:17 PM9/21/18

to jenkinsc...@googlegroups.com

Jesse Glick commented on

Filed PR with a basic display for classic UI. 2015-09-11 comments, as well as some miscellaneous fixes such as adding a wipe out workspace link, need to be refiled as separate issues, but I think this captures the most common and obvious request.

dnusbaum@cloudbees.com (JIRA)

unread,

Dec 13, 2018, 1:41:05 PM12/13/18

to jenkinsc...@googlegroups.com

Devin Nusbaum commented on

A way to easily view all of the workspaces for a specific build (the fourth bullet point in the description) was just added in version 2.24 of Pipeline Supporting APIs Plugin as a sidebar link named Workspaces on the build page.

david@famriemens.nl (JIRA)

unread,

May 8, 2019, 3:14:36 AM5/8/19

to jenkinsc...@googlegroups.com

David Riemens commented on

Is there now a means to get the "workspace URL of multi branch pipeline jenkins projects" programmatically ? Such that I can:

add it into an email
expose it even within the job itself
in the tests we are running I want to print an URL to the workspace for failing tests.

Yes, I can navigate by hand to the workspace via the pipeline steps, but that is very cumbersome with 8 (or more) parallel branches.
I've even added a hard-code lookup table in my script, but that breaks as soon as I start multiple of the same jobs.

NB: when I hover the mouse over the "Allocate node : Start" message, I do get a popup with "ID: 71" or so. All I need is that ID number within my "node {}" block ..

someone please,,,

david@famriemens.nl (JIRA)

unread,

May 17, 2019, 1:28:30 AM5/17/19

to jenkinsc...@googlegroups.com

David Riemens commented on

Devin Nusbaum : would you have an idea ? Just needed to update my pipeliine scripts, and again the ID's changed...

dnusbaum@cloudbees.com (JIRA)

unread,

May 28, 2019, 12:51:51 PM5/28/19

to jenkinsc...@googlegroups.com

Devin Nusbaum commented on

David Riemens The fix to this ticket created a new page that lists all workspaces used by the build which is always accessible via a URL like <JENKINS_HOST>/jobs/<JOB_NAME>/<BUILD_NUMBER>/ws, which might be good enough for your purposes.

If you really need to construct a link to the current workspace inside of of a Pipeline, my recommendation would be to create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs. Either way, it would be better to create a new RFE or discuss on the mailing list rather than commenting on this ticket.

dnusbaum@cloudbees.com (JIRA)

unread,

May 28, 2019, 12:52:03 PM5/28/19

to jenkinsc...@googlegroups.com

david@famriemens.nl (JIRA)

unread,

Oct 16, 2019, 5:58:05 AM10/16/19

to jenkinsc...@googlegroups.com

David Riemens commented on

Devin Nusbaum : can you point me to an example to "create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs" ? I would not have an idea how to get that.

For now I implemented a dirty workaround: I made a script that fetches (wget) the .../lastBuild/flowGraphTable page, and extracts the lines have the info that I need.
This script I call from my job and generate a table of the numbers (the ID's) that I need. This is obviously far from perfect, but hopefully is sort of auto-correcting.

I still am hoping for a simple currentBuild.Info.something.ID solution ...