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

PlasticSCM - Workspace Null Parameter

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • plasticscm-plugin
    • Our Environment details as follows,
      Jenkins Master Server OS: Ubuntu-12.04 LTS (64 Bit).
      Jenkins Version: 2.46.2
      PlasticSCM Plugin Version - 2.9
      Master & Slave Based.
      Slave Machine: Windows-7 (64-Bit)
    • plasticscm-plugin-2.14

      Dear Team,

      Recently I have upgraded our Jenkins master server to 2.46.2 version. Previously we have configured few jobs with PlasticSCM and it was working fine till before upgrade.

      Now the problem is with the new PlasticSCM Plugin Version - 2.9 under “Workspace name” made as mandatory. By default it configured with - Jenkins-${JOB_NAME}-${NODE_NAME} variable.

      Due to this it additionally creates one more folder inside the workspace/jobname location. Eg: It is creating like D:\Jenkins\workspace\17_Mohan_Test\17_Mohan_Test\

      Is there any way to make this “Workspace name” null? As I have already defined under Manage Jenkins->configure system->Workspace Root Directory as - ${ITEM_ROOTDIR}/workspace.

      So under Job PlasticSCM “Workspace name” I want to make it as null, So kindly help me.

      Thanks,
      Mohan

          [JENKINS-44147] PlasticSCM - Workspace Null Parameter

          Miguel González added a comment -

          Hi!

          Is this issue related to JENKINS-50284? The shared libraries issue was already fixed in version 2.22.

           

          Regardless of that, what you probably want is to get rid of the checkout subdirectory, right? You can achieve that by leaving the "use multiple workspace" checkbox unchecked.

           

          Could you please try that and let us know if that fixes the issue?

          Thank you!

           

          Regards,

          Miguel

          Miguel González added a comment - Hi! Is this issue related to JENKINS-50284 ? The shared libraries issue was already fixed in version 2.22.   Regardless of that, what you probably want is to get rid of the checkout subdirectory, right? You can achieve that by leaving the "use multiple workspace" checkbox unchecked.   Could you please try that and let us know if that fixes the issue? Thank you!   Regards, Miguel

          Miguel González added a comment -

          The described functionality was already released in plugin version 2.14.

          Miguel González added a comment - The described functionality was already released in plugin version 2.14.

            mig42 Miguel González
            smohan08 Mohan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: