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

[Pipeline] Optionally disable suffixed workspace paths for custom workspaces

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      It seems counter-intuitive that even when specifying a custom workspace you might still get one appended with a suffix such as "@2".

      Could there be an option either at the Jenkins or job level to disable using the lease workflow when using custom workspace, so that we can guarantee that we get the workspace specified?

      This is the behavior we've come to expect that was default in AbstractBuild.

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ssutherland Sean Sutherland
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: