![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Attachments:
|
2014-10-03_1034.png |
|
Components:
|
core |
|
Created:
|
03/Oct/14 8:46 AM
|
|
Description:
|
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
|
|
Environment:
|
Jenkins v1.582 / Debian 7
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Blocker]() Blocker
|
|
Reporter:
|
tristan bessoussa
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
