|
||||||||
|
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.
[Edit: Apologies for the upset tone. This comment was entered in the heat of disaster recovery.]
Just a comment: This change caused a major downtime in my organization. We had scripts to rsync the build artifacts to a network location for release. This change caused the released files to be inaccessible to users. Worse, because we were in the same group as the Jenkins user, we were delayed diagnosing the issue.
Blindly changing the umask used by the whole process seems like a very inappropriate response to a targeted issue.
Until now, we had good luck with the Jenkins tip in production. We can not longer say that it is safe to do so.