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

Shared Workspace with empty Name becomes the default Shared Workspace in new jobs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • Jenkins 2.21

      If, under Configure System, a new entry is created for Workspace Sharing and it is not given a Name or Repository URL (i.e. left blank), it is still useable as a shared workspace. However when new Freestyle jobs are created they now default to using this shared workspace. This has unintended consequences as users do not realise they need to select "None" under a job's Shared Workspace config section. If they fail to do this, the job will use the shared workspace, which is unexpected and a source of problems.

      If a name is defined, new jobs no longer default to this workspace - they default to None instead, as I believe the should.

            Unassigned Unassigned
            dantliff David Antliff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: