• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • branch-api-plugin
    • None

      An older version of Jenkins used follow directory "Workspace Root Directory" to create the a job directory and than a branch directory to build the job.

      for example:
      WorkspaceDir -->
      /home/jenkins/workspace/Chamaeleon_Build_arm-Linux_AK

      with follow subdirectories:
      develop
      feature%2Fmetering
      master
      release%2Ftest

      With a newer version of Jenkins the follow directories are used with some crypted names and into the jenkins root dir:
      JenkinsHome -->
      /var/lib/jenkins/workspace/

      86-Linux_AK_feature_data1gw-ZPRTIMQMR37ERO34LWTIX3MDWNDF2BVSVQYCGAPMABRNIZF4JHGA
      AK_feature_nsd_with_d2pcomd-4OSVVPXMSLGJQT56SR4PP4LHLDDTIRLCOH6NFM7JPJZOM45C66UA
      AK_feature_nsd_with_d2pcomd-J6LMD7PVYENPVFHFM3TWMMKYKS6KB5NPGAO47LGD2TINXUC5GC2Q
      AK_feature_nsd_with_d2pcomd-J6WBJOADOZSXYNEYPLCPB5GQ4Z5D7WDAHN3EPZC5YKCHF5EP6IMA
      AK_feature_nsd_with_d2pcomd-QDAQYEZDKUYUVTZCRL73UJDDQJ4AUHKSLNW23OAEFXIBZ2IJYPJA
      AK_feature_nsd_with_d2pcomd-QLNZT4GTX57IUCNQSVTNMPX6PUSC5PAI44UIMGC7MX4QGHKDLQ5A
      AK_feature_nsd_with_d2pcomd-WTEXDHTZQXBOKOMMQDIJV3GM5JYCRFRUMML3BDHT4XL7MOBOD7UA
      _AK_feature_odb_eventssytem-3E37LF3TCTSS6BNP5J7RXFKUDKUYR2GPC365IR275MK45QJYY2MA
      _AK_feature_odb_eventssytem-4G34MXDNEOHNCXWP7MGD6SPYUBJGURHJIGTC6DNUEHELTTXOBFEQ
      _AK_feature_odb_eventssytem-5FQCEOG4WSLPLKNJMS6HESPQ7RBOOLN2WTLGDHBBZCQGCRO7TO5A
      _AK_feature_odb_eventssytem-CN6SG7RZXPIKAG54WEQO2XLGI4IZUGSBF5ZYWQRMQPWC3KSYMLDQ
      _AK_feature_odb_eventssytem-H7R3Z2MBUSRJQVJUUEVLJMZGMT6N2OPX6R6UNIRBW7MEPCPFOV5A
      _AK_feature_odb_eventssytem-XA42V4BXCMLNMTTPEPLY64ELIT2ARXGHM5TS4IL6Q44RRVR7PSBA
      amaeleon_Doxygen_AK_develop-JBOKHZQ65MSKCNMJJZHKTV5NFPOILZ5PIJ3IW4BBRGSEHR4YIX7A
      _Build_arm-Linux_AK_develop-5FZX4TMGW2CSMHBV6I5KYNQJY4IBOGW74XWMUYNIMR26SXBTEAEA
      _Build_x86-Linux_AK_develop-F6Y47TRMIEQG5NDNVFXMQMQAHQTHMJDOVUYQUJ2BP4Q5IMWTKUOQ

      Please correct the directory to the old behaviour.

          [JENKINS-40072] Multibranch creates multiple new directories

          twolfart added a comment -

          Workaround in JENKINS-38706.

          twolfart added a comment - Workaround in JENKINS-38706 .

          Is this the workaround?

          -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0

          And does it return to the previous behavior described in the issue? I went through quite a roll back since this feature got introduced and would not want to update plugins again before making sure it is fixed.

          Alexander Siniouguine added a comment - Is this the workaround? -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 And does it return to the previous behavior described in the issue? I went through quite a roll back since this feature got introduced and would not want to update plugins again before making sure it is fixed.

          just testing with the latest version 2.41 and all plugins updated: with that workaround, folders are created as per the old hierarchy, BUT still creating 3 folders per branch (<branch_name>, <branch_name>@script, <branch_name>@tmp), and then, when Jenkins triggers the build, it's in the wrong dir (in the first one which is empty, while the code was checked out in the @script one).

          is there any workaround to this side effect ? thanks

          nicolas mettais added a comment - just testing with the latest version 2.41 and all plugins updated: with that workaround, folders are created as per the old hierarchy, BUT still creating 3 folders per branch (<branch_name>, <branch_name>@script, <branch_name>@tmp), and then, when Jenkins triggers the build, it's in the wrong dir (in the first one which is empty, while the code was checked out in the @script one). is there any workaround to this side effect ? thanks

            stephenconnolly Stephen Connolly
            andrekalb Andre Kalb
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: