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

Plastic-SCM duplicate workspace names

    Details

    • Similar Issues:

      Description

      This bug involves workspaces names and the PlasticSCM plugin for Jenkins. 

      If two different Jenkins projects have a workspace with the same name, then building one will delete the files from the other one. This is due to the fact that Plastic cannot have duplicate workspace names.

      In the logs:

      15:55:43 WNAME#XXXXX#c:\JenkinsBuilds\NAME\bStompTest\workspace\WNAME
      15:55:43 [WNAME] $ "C:\Program Files\PlasticSCM5\client\cm" rmwk wk:WNAME
      15:55:43 The workspace WNAME has been deleted.
      15:55:43 [WNAME] $ "C:\Program Files\PlasticSCM5\client\cm" rmwk wk:WNAME
      15:55:43 The workspace WNAME has been deleted.
      15:55:45 [WNAME] $ "C:\Program Files\PlasticSCM5\client\cm" mkwk WNAME C:\JenkinsBuilds\NAME\aStompTest\workspace\WNAME –

       In this example, aStompTest and bStompTest both have a workspace name defined as WNAME. aStompTest is building, but the rmwk deletes the bStompTest directory.

      Possible solutions:

      1. Use Plastic's "cwk" command in this case. This will re-define the location of the Plastic workspace to a new directory. 

      2. Automatically rename duplicate workspace names 

      See also: http://www.plasticscm.net/index.php?/topic/3485-jenkins-plastic-plugin-confused-by-duplicated-workspace-names-between-projects/

       

        Attachments

          Activity

          Hide
          mig42 Miguel González added a comment -

          We're currently working in major functionality changes in plasticscm-plugin. Our goal is to eventually make workspace names randomly generated and render them useless for the plugin functionality.

           

          That way we'll avoid workspace name collision and this kind of issues entirely.

          Show
          mig42 Miguel González added a comment - We're currently working in major functionality changes in plasticscm-plugin. Our goal is to eventually make workspace names randomly generated and render them useless for the plugin functionality.   That way we'll avoid workspace name collision and this kind of issues entirely.

            People

            • Assignee:
              mig42 Miguel González
              Reporter:
              amcilvaine Abraham McIlvaine
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: