michaelhuettermann Please check out what an epic is about before using it in your issues. This is specifically about the AWS Lambda Plugin.

Hi danielbeck, thanks for removing the epic reference. Actually, I did not want to reference one at all, initially, because I'm not aware of how you slice your organization, and I just wanted to give feedback on this user experience.

I just wanted to give feedback on this user experience.

Thanks for that, that's awesome of you!

I just posted the comment so you know you don't need to make the effort for future issues you file.

Hi danielbeck and team,
thanks!! It is impressive how you take care and how intensive you're are working on Jenkins to make the product even more sophisticated. I've never believed that this could be possible, but Jenkins 2 has some really thrillling new features.

The workspace is browseable via a specific build number/run, which then lets you pick a step to find its workspace (eg you click on node, to browse the workspace). You have to know to look at steps however.

Perhaps on the build results page there could be a link to "Browse workspace" that explains this (with a link to the steps).

Workspace browsing is different by nature in pipeline as Oleg explains, and much more complex to find where things are, perhaps having it "hard to find" is not a bad thing so people don't rely on it.

Otherwise, there needs to be a way to roll up all workspaces used and present them in a list.

I'm also looking for a way to browse the workspaces involved. But I do not see any clickable node when looking at the build number/run??? Am I missing some configuration or plugin?

Pipeline Steps

I use the jenkins workspace as a yum repo and I was very keen on migrating to Pipeline as code but not having a permalink makes it very difficult as there is no way of browsing / accessing the created files.

I'd like to give a link to the Workspace within notification email, and I find no reliable way to do it simply.
Also, it is really a mess to have no Workspace link on each build page, at least as long as the workspace directory still exists.

I'd like to give a link to the Workspace within notification email, and I find no reliable way to do it simply.

I do not know of a reliable way to do that. Probably better to just link to the build URL, and wait for JENKINS-26138 to be implemented.