- 26 9月, 2014 5 次提交
-
-
由 Michael Neale 提交于
also requires no signalling of the process and less risk of (ironically) lost logs which postrotate attempts to address.
-
由 CloudBees DEV@Cloud 提交于
-
由 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.
-
由 Jesse Glick 提交于
Also sending the exception to the log, which is where plugin developers expect to see it. (This is also necessary for the exception to be visible say from configRoundtrip in a functional test. Otherwise you just see a FailingHttpStatusCodeException due to the 400 error code, with no details.) Might actually suffice to just throw a ServletException wrapping the exception up the chain, letting Stapler or the container handle it, but this change is more conservative.
-
由 Jesse Glick 提交于
sendError(Exception…) should set the exception attribute on the response, since error.jelly handles this nicely.
-
- 25 9月, 2014 3 次提交
-
-
由 Nicolas De Loof 提交于
-
由 Jesse Glick 提交于
… hudson.tasks.Shell$DescriptorImpl getShellOrDefault WARNING: Remote call on …@docker failed
-
由 Jesse Glick 提交于
Noting that CloudSlaveRetentionStrategy appears to be a poor reimplementation of CloudRetentionStrategy.
-
- 24 9月, 2014 8 次提交
-
-
由 Jesse Glick 提交于
[FIXED JENKINS-22769] ItemListener callbacks should run as SYSTEM since they sometimes do ACL-checked calls.
-
由 Nicolas De Loof 提交于
-
由 Jesse Glick 提交于
https://bugs.openjdk.java.net/browse/JDK-6933067 claims to be fixed as of Java 6, our baseline.
-
由 Nicolas De Loof 提交于
-
由 Jesse Glick 提交于
Assertions are only for cases where you believe the failure of the condition is impossible. For cases where external code might mistakenly make an incorrect call, throw an exception.
-
由 Nicolas De Loof 提交于
-
由 Harald Albers 提交于
Update the link to the Jetty documentation in realm.properties
-
由 Kohsuke Kawaguchi 提交于
The actual fix is made in 040b7d40 through winp.
-
- 23 9月, 2014 6 次提交
-
-
由 Emmanuel Bourg 提交于
-
由 Stephen Connolly 提交于
-
由 Kohsuke Kawaguchi 提交于
This version checks the critical flag of the process, as killing such a process results in BSoD.
-
由 Kohsuke Kawaguchi 提交于
-
由 CloudBees DEV@Cloud 提交于
-
由 Jesse Glick 提交于
-
- 22 9月, 2014 9 次提交
-
-
由 Oliver Gondža 提交于
Update package name reference.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Amaury 提交于
Update package name reference from Hudson to Jenkins.
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 18 9月, 2014 9 次提交
-
-
由 Daniel Beck 提交于
-
由 Daniel Beck 提交于
Explicitly set the umask for daemon in Debian init script
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Paul Kilgo 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Paul Kilgo 提交于
-
由 Paul Kilgo 提交于
As discovered by danielbeck in #jenkins, daemon(1) does not inherit the parent process's umask. The --umask flag is the means to set it explicitly.
-
由 Jesse Glick 提交于
-