- 23 4月, 2015 3 次提交
-
-
由 Oleg Nenashev 提交于
This reverts commit b6c7b83e.
-
由 Oleg Nenashev 提交于
This reverts commit 4ddeeb84.
-
由 Kohsuke Kawaguchi 提交于
Advertise X-JNLP-Host-Name correctly
-
- 21 4月, 2015 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
This allows TCP slave agent port to be reverse proxied.
-
由 Jesse Glick 提交于
-
- 20 4月, 2015 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 David Hoover 提交于
-
- 17 4月, 2015 2 次提交
-
-
由 Kamran Mackey 提交于
Signed-off-by: NKamran Mackey <kamranm1200@gmail.com>
-
由 Jesse Glick 提交于
-
- 15 4月, 2015 4 次提交
-
-
由 Jesse Glick 提交于
-
由 David Hoover 提交于
-
由 Oleg Nenashev 提交于
BIGNUMBER_STAR mode has been selected, because it utilizes GNU extensions (like LONGFILE_GNU does).
-
由 Oleg Nenashev 提交于
-
- 14 4月, 2015 2 次提交
-
-
由 Oleg Nenashev 提交于
This test also introduces additional round-trip tests for small files
-
由 David Hoover 提交于
-
- 13 4月, 2015 3 次提交
-
-
由 Stephen Connolly 提交于
[FIXED JENKINS-27708][FIXED JENKINS-27871] Ensure that identification of blocked tasks is using the live state. - The creation of a snapshot itself should be relatively cheap given the expected rate of job execution. You probably would need 100's of jobs starting execution every iteration of maintain() before this could even start to become an issue and likely the calculation of isBuildBlocked(p) will become a bottleneck before updateSnapshot() will. Additionally since the snapshot itself only ever has at most one reference originating outside of the stack it should remain in the eden space and thus be cheap to GC. - JENKINS-27708 comments 225819 and 225906 provide more complex but logically equivalent fixes of this issue. I am favouring this approach as it is simpler and provides less scope for error as any new helper methods can just rely on the snapshot being up to date whereas with the other two candidates if a new helper method is introduced there is the potential to miss adding support for the live view. The comment 225819 has the risk of introducing extra lock contention while the comment 225906 version forces every access to the helper methods to pass a second memory barrier
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 12 4月, 2015 6 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
- 11 4月, 2015 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 07 4月, 2015 2 次提交
-
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
Without this change you need to do: ``` User user; final SecurityContext oldContext = ACL.impersonate(a); try { user = User.current(); } finally { SecurityContextHolder.setContext(oldContext); } ``` Which seems incredibly wasteful. Or else you need to replicate the logic in User.current() which makes that code hard to change.
-
- 06 4月, 2015 2 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
- 05 4月, 2015 1 次提交
-
-
由 Oliver Gondža 提交于
-
- 03 4月, 2015 2 次提交
-
-
由 Oliver Gondža 提交于
-
由 Kohsuke Kawaguchi 提交于
This reverts commit fe1a1487. It's been about a month, so I think it has served its purpose.
-
- 02 4月, 2015 1 次提交
-
-
由 Jesse Glick 提交于
-
- 01 4月, 2015 2 次提交
-
-
由 Jesse Glick 提交于
-
由 Jesse Glick 提交于
-
- 31 3月, 2015 4 次提交
-
-
由 Jesse Glick 提交于
Allowing some methods to be overridden, with the caveat that the overrides will not be called from CoreWrapperStep.
-
由 Jesse Glick 提交于
-
由 Stephen Connolly 提交于
-
由 Kohsuke Kawaguchi 提交于
-