[Regression] Default permission when archiving a build

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Hi,

      It seems that there a regression with a recent patch.
      Whem i'm building my application, and archiving it in order to deploy the application, the default permission seems to have changed in *a bad way*.

      You can see the screenshot attached that the v1.0.6 has "normal" permission but after a jenkins update, the version 1.0.8 on the screenshot have really weird permissions which prevent the webserver from reading the content of the folder.
      (i had to manually set the correct permissions for 1.0.9)

      I didn't touch the build script responsible of building the archive or the deployment method between those versions.

      I suspect the umask PR thing to be the cause (but this is just a guess) : https://github.com/jenkinsci/jenkins/pull/1397

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            tristan bessoussa
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: