Currently control files are generated in a subdirectory of the workspace. This is causing various issues because some build steps are not expecting these extra files which are internal to Jenkins.

      These could be generated instead in a temporary directory or in a specific subfolder of the slave root instead.

          [JENKINS-27152] Store sh control files outside of workspace

          Vincent Latombe created issue -
          Vincent Latombe made changes -
          Summary Original: Store bourneshell control file outside of workspace New: Store bourneshell control files outside of workspace
          Vincent Latombe made changes -
          Link New: This issue is related to JENKINS-26105 [ JENKINS-26105 ]
          Vincent Latombe made changes -
          Remote Link New: This issue links to "[jenkins-users] Workflow Plugin - Performing a Release (Web Link)" [ 12127 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26133 [ JENKINS-26133 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-30240 [ JENKINS-30240 ]
          Jesse Glick made changes -
          Labels Original: robustness workflow New: api docker robustness workflow
          Jesse Glick made changes -
          Summary Original: Store bourneshell control files outside of workspace New: Store sh control files outside of workspace
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-30884 [ JENKINS-30884 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 11 (Web Link)" [ 13534 ]
          Cyrille Le Clerc made changes -
          Link New: This issue is blocking JENKINS-32624 [ JENKINS-32624 ]

            jglick Jesse Glick
            vlatombe Vincent Latombe
            Votes:
            7 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: