Concurrent build jobs use BAD naming convention for workspaces

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major
    • Component/s: remoting
    • Environment:
      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"

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

              Created:
              Updated:
              Resolved: