• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Centos 5.6, 32-bit, JDK 7u3, Jenkins 1.455

      I've seen several related and/or resolved issue on this but I wasn't sure which one was relevant for re-opening.

      I have a very basic job (name DEV) that polls a git repository, deploys the files to a local webserver via a shell script, then archives the workspace. A second job then picks up the last successful archive w/ the Copy Artifact plugin and attempts to run the same deploy script and receives an error due to missing executable permissions. The intent is to put a skeleton together of a pipeline for DEV->QA->PROD, each deploying to a local folder (symlinked to a directory apache is aware of), the file permissions are deployment scripts are managed in the repository with the source for the site.

      I initially thought this was an issue with the Copy Artifact plugin, but after writing a basic shell script to manually copy the files and then looking directly at the archive folders in the job folders, it appears to be the Archive operation itself.

      It appears that all the file and folder permissions are being set/cleared when the archive occurred. The contents of the DEV workspace has original permissions after a run, but the archive contents (jenkins\jobs\DEV\builds##\archive) are missing their permissions. All files have been set to 644, all directories to 755 (>2000 files in multiple subdirectories, although to be fair I've only checked 5 or 6 subdirectories).

      This is similar to the related set of tickets under JENKINS-9397 but I wasn't sure which (if any) was best to reopen.

          [JENKINS-13128] Artifacts Permissions Stripped

          Eli Weinstock-Herman created issue -

          evernat added a comment -

          Is it reproduced with a recent Jenkins version?

          evernat added a comment - Is it reproduced with a recent Jenkins version?

          I can confirm that this is still an issue on v1.523

          Brandon Rochon added a comment - I can confirm that this is still an issue on v1.523

          Daniel Beck added a comment -

          Would be interesting to see whether this occurs only when building on master, or also when building on a slave node. (A similar issue is known to occur with file modification time stamps and that changes behavior there.)

          Daniel Beck added a comment - Would be interesting to see whether this occurs only when building on master, or also when building on a slave node. (A similar issue is known to occur with file modification time stamps and that changes behavior there.)
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-23645 [ JENKINS-23645 ]

          Tony Panza added a comment -

          @Daniel This occurs on slave nodes as well. On a slave with Ubuntu 10.04.3 LTS (2.6.32-64-generic-pae #128-Ubuntu SMP Tue Jul 15 08:49:38 UTC 2014 i686 GNU/Linux), Jenkins v1.436.

          Tony Panza added a comment - @Daniel This occurs on slave nodes as well. On a slave with Ubuntu 10.04.3 LTS (2.6.32-64-generic-pae #128-Ubuntu SMP Tue Jul 15 08:49:38 UTC 2014 i686 GNU/Linux), Jenkins v1.436.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 143591 ] New: JNJira + In-Review [ 175948 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-38274 [ JENKINS-38274 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-14269 [ JENKINS-14269 ]
          Aaron D. Marasco made changes -
          Link New: This issue is related to JENKINS-9397 [ JENKINS-9397 ]

            jvz Matt Sicker
            tarwn Eli Weinstock-Herman
            Votes:
            7 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: