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

When workspace is cloned, exec permissions on files are wiped out


      1. Create a job that e.g. checks out and builds some code. Some of the resulting files are executable binaries.
      2. Set this job to archive its workspace for cloning by other jobs (using the Clone Workspace SCM plugin).
      3. Create a new job that uses the other job's cloned workspace as its SCM/code source.
      4. Run this job.

      Result: The workspace of the second job will have a copy of all the files from the first job's workspace, but the binaries have all lost their exec permissions. The new job has to manually chmod those files if it wants to exec them.

            abayer Andrew Bayer
            owenmehegan Owen Mehegan
            0 Vote for this issue
            1 Start watching this issue