- 10 10月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-25074] Make sure to call Job.getBuildHealthReports just once per t:buildHealth render.
-
由 Kohsuke Kawaguchi 提交于
Based on the reaction to these issues and JENKINS-24514, I'm partially reverting the original change, and bringing the umask default back to 022. The configurable option does enable the user to choose a different umask, so I think I can still claim that JENKINS-24514 is addressed.
-
- 08 10月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
- 06 10月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 02 10月, 2014 3 次提交
-
-
由 Daniel Beck 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 29 9月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 26 9月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
The primary change is that the thread name update code now lives in a filter instead of 'Stapler' servlet, so it happens a lot earlier.
-
- 24 9月, 2014 3 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-22769] ItemListener callbacks should run as SYSTEM since they sometimes do ACL-checked calls.
-
由 Nicolas De Loof 提交于
-
由 Kohsuke Kawaguchi 提交于
The actual fix is made in 040b7d40 through winp.
-
- 23 9月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
This version checks the critical flag of the process, as killing such a process results in BSoD.
-
- 22 9月, 2014 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 18 9月, 2014 4 次提交
-
-
由 Daniel Beck 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 17 9月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
-
- 16 9月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Integrated the fix in remoting to Jenkins 1.580.
-
- 15 9月, 2014 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 14 9月, 2014 2 次提交
-
-
由 Daniel Beck 提交于
-
由 Daniel Beck 提交于
-
- 13 9月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
-
- 08 9月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
-
- 07 9月, 2014 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 06 9月, 2014 4 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Daniel Beck 提交于
-
由 Daniel Beck 提交于
-
由 Daniel Beck 提交于
-
- 01 9月, 2014 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 30 8月, 2014 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
Ubuntu (at least as of 12.04) has the default umask 022, which made some users nervous. Quoting its /etc/login.defs below, which explains its historical origin: UMASK is the default umask value for pam_umask and is used by useradd and newusers to set the mode of the new home directories. 022 is the "historical" value in Debian for UMASK 027, or even 077, could be considered better for privacy There is no One True Answer here : each sysadmin must make up his/her mind. It does seem to me that a bit more restrictive default is sensible, so this change introduces /etc/default/jenkins parameter that sets the default umask to 027 to prevent "others" from seeing files. Not that keys and other sensitive files are protected anyway, so it is not the case that the privacy of Jenkins data files have been vulnerable prior to this change.
-
由 Jesse Glick 提交于
[FIXED JENKINS-23522] Defend against stack overflows when a listener (unnecessarily) called super from a deprecated method. Fixes #1295 a little differently.
-
- 29 8月, 2014 1 次提交
-
-
由 Daniel Beck 提交于
-
- 27 8月, 2014 2 次提交
-
-
由 Jesse Glick 提交于
-
由 Daniel Beck 提交于
-