|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I wasn't excepting a BC break on a minor update, but my bad on this.
Unfortunatly,
1) I commented the umask in `/etc/default/jenkins` as advised
2) I restarted jenkins `service jenkins restart`
3) I rebuilt the release of v1.0.9 of my application.
The result is the same after extract:,
`drwxr-x--- 12 jenkins jenkins 4096 Oct 1 18:08 v1.0.9`
I tried this again and before launching the build, I ereased all previous v1.0.9 archieved builds. The result is the same.
Does umask need to be set at a particular version to restore original settings ? Or do I need to reset my whole workspace so it can git clone with correct file/folder permission ? (The date still refer to the first time I built this tag)
Thanks for your help![]()
.