Comments on: where did the workspace go in jenkins pipelines

By: Steve

Steve — Tue, 10 Dec 2019 16:10:18 +0000

A critical step is to click on an ‘allocate node: start’ link. The author does include this, but I glossed over it. I clicked on the link where my build failed; which seems like the right choice to me. But there is no workspace link under that. The workspace link is only on the ‘allocate node: start’ page.

Further, as hinted by “If you have multiple nodes, you’ll need to do this more than once” you need to choose the right allocate link or try each one to find the one you want. I assume you want the link that is at the top of the hierarchy for the step that failed.

By: How to view Jenkins workspace on a Pipeline job? – Config9.com

How to view Jenkins workspace on a Pipeline job? – Config9.com — Thu, 12 Sep 2019 01:34:37 +0000

[…] Check out this link it shows how to get the workspace when you are using jenkins pipeline: https://www.selikoff.net/2016/07/10/workspace-jenkins-pipelines/ […]

By: Frank Jakobsen

Frank Jakobsen — Tue, 09 Oct 2018 08:27:09 +0000

@hyos: I’m a novice, so following your advice, I just replaced the whole script with one line containing the cleanWs() or deleteDir(). That didn’t work. Could you please show a complete example as it should be in the pipeline edit box?

By: hyos

hyos — Mon, 07 Aug 2017 11:46:13 +0000

or deleteDir() should do the same

By: hyos

hyos — Mon, 07 Aug 2017 11:45:20 +0000

@Jeanne Boyarsky but you absolutely can, go into the last build, hit replay, replace pipeline with cleanWs(), run once.

By: Jeanne Boyarsky

Jeanne Boyarsky — Sun, 19 Feb 2017 16:09:43 +0000

@gsnerf: True. I don’t want to clean the workspace automatically though. I want to do it on demand manually like I used to be able to. That way the workspace is there after for review, but I can clean it out as needed

By: gsnerf

gsnerf — Fri, 17 Feb 2017 12:11:45 +0000

That info is not completely correct, you can use step([$class: ‘WsCleanup’]) in your pipeline to clean the workspace automatically

By: graham

graham — Thu, 09 Feb 2017 13:23:13 +0000

thanks!

on disk the workspace is now in ~jenkins/workspace, rather than buried under jobs. but there’s more than one per job now, which means you have to work out which one belonged to that build