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

Concurrent build jobs use BAD naming convention for workspaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • remoting
    • Windows XP 32 nit
      Jenkins ver. 1.473
      SVN 1.6x

      Jobs fail if they are allowed to run concurrent if svn commands are used in the build steps like shell/windows batch.

      Reason is the "@" appended to the workspace name which indicates svn pegging.
      All jobs running in "workspace" succeed all jobs running in "workspace@2" and upwards fail with the message "is not a working copy"

          [JENKINS-14354] Concurrent build jobs use BAD naming convention for workspaces

          Kohsuke Kawaguchi added a comment -

          You can override the separator by specifying the system property "hudson.slaves.WorkspaceList". For example, -Dhudson.slaves.WorkspaceList=_

          Kohsuke Kawaguchi added a comment - You can override the separator by specifying the system property "hudson.slaves.WorkspaceList". For example, -Dhudson.slaves.WorkspaceList=_

            Unassigned Unassigned
            kopfwunde Jan Seidel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: