Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33839

Pipeline workspace is not browsable via pipeline page

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Minor Minor
    • pipeline

      On the Jenkins project web page, a Pipeline does not offer its workspace.
      Please propagate and enable browsing of the workspace of the Pipeline.

          [JENKINS-33839] Pipeline workspace is not browsable via pipeline page

          Michael Hüttermann created issue -
          Michael Hüttermann made changes -
          Epic Link New: JENKINS-33198 [ 168576 ]

          Oleg Nenashev added a comment -

          It's a bit complicated, because Pipeline does not have workspace by default. On the other hand, it may utilize multiple workspaces by calling node() and workspace() multiple times.

          Anyway, I'll fix the component

          Oleg Nenashev added a comment - It's a bit complicated, because Pipeline does not have workspace by default. On the other hand, it may utilize multiple workspaces by calling node() and workspace() multiple times. Anyway, I'll fix the component
          Oleg Nenashev made changes -
          Component/s New: workflow-plugin [ 18820 ]
          Component/s Original: pipeline-view-plugin [ 21435 ]
          Oleg Nenashev made changes -
          Assignee Original: Sergei Egorov [ bsideup ] New: Jesse Glick [ jglick ]
          Daniel Beck made changes -
          Epic Link Original: JENKINS-33198 [ 168576 ]

          Daniel Beck added a comment -

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

          Daniel Beck added a comment - michaelhuettermann Please check out what an epic is about before using it in your issues. This is specifically about the AWS Lambda Plugin.

          Michael Hüttermann added a comment -

          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.

          Michael Hüttermann added a comment - 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.

          Daniel Beck added a comment -

          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.

          Daniel Beck added a comment - 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.

          Michael Hüttermann added a comment -

          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.

          Michael Hüttermann added a comment - 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.

            jglick Jesse Glick
            michaelhuettermann Michael Hüttermann
            Votes:
            0 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: