- 12 7月, 2013 4 次提交
-
-
由 Christoph Kutzinski 提交于
[FIXED JENKINS-18671] Clock Difference broken on Manage Nodes page
-
由 Jesse Glick 提交于
-
由 Richard Mortimer 提交于
-
由 Richard Mortimer 提交于
against incorrect values if times are ever compared between different JVM nodes
-
- 11 7月, 2013 1 次提交
-
-
由 Richard Mortimer 提交于
System.nanos() returns a monotonically increasing value that is not related to wallclock time. Use System.currentTimeMillis() instead.
-
- 10 7月, 2013 2 次提交
-
-
由 Jesse Glick 提交于
Unlike the bug I originally reproduced, in which the parent had some builds but the context in which the new build was scheduled omits a parent, this seems to be due to a case in which there is no build record at all for the parent. No idea how that could happen (getLastBuild should return even a running, failed, or aborted build), but @treydock reports a stack trace in 1.509.2 which implies this. So fixing null safety; will not prevent an exception but will report it more gracefully.
-
由 Harald Albers 提交于
-
- 09 7月, 2013 2 次提交
-
-
由 Oliver Gondža 提交于
-
由 Jesse Glick 提交于
Going back in browser history can reset configuration form to the *previous* state, not what was just saved! (In the case of lazily inserted form elements.) Thus clicking Save from that page would actually revert your recent changes. For now, just omitting the button; could make it go back to index or configuration pages, but there are already links for this.
-
- 08 7月, 2013 4 次提交
-
-
由 Stephen Connolly 提交于
-
由 Nicolas De Loof 提交于
-
由 Nicolas De Loof 提交于
-
由 Nicolas De Loof 提交于
-
- 07 7月, 2013 4 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
Conflicts: core/src/main/java/hudson/model/AbstractProject.java
-
由 Kohsuke Kawaguchi 提交于
-
- 06 7月, 2013 8 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Christoph Kutzinski 提交于
-
由 Christoph Kutzinski 提交于
This helps a lot when mocking AbstractProject in unit tests, because so I don't have to suppress the constructor with PowerMockito
-
由 Christoph Kutzinski 提交于
-
由 Christoph Kutzinski 提交于
[JENKINS-14585] core side fix for: claim-plugin cannot claim broken tests in maven jobs
-
由 ssogabe 提交于
-
- 05 7月, 2013 4 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
The earlier fix by @ssogabe broke the test. This fix corrects the problem properly. The reason this error happens with some plugins is that if there's an input field whose name is "on", then even after prototype.js extends an element object, "form.on" will refer to the input element, not the prototype.js function to add an event handler.
-
由 Kohsuke Kawaguchi 提交于
-
- 04 7月, 2013 5 次提交
-
-
由 Nicolas De Loof 提交于
-
由 Nicolas De Loof 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
(cherry picked from commit d8f74cf8)
-
由 Kohsuke Kawaguchi 提交于
-
- 03 7月, 2013 6 次提交
-
-
由 Christoph Kutzinski 提交于
-
由 Stephen Connolly 提交于
If every node is restricted to tied jobs only, Matrix build jobs can never start
-
由 Stephen Connolly 提交于
-
由 Stephen Connolly 提交于
- Fixes a regression in core where the display name clear on copy was triggering a save - More than one way to do this, could also have used the marker interface approach This route seems slightly less fragile, though people could still add ItemListeners with order == -Double.MAX_VALUE which would then introduce intdeterminism. A marker interface would remove that indeterminism as the onCopyComplete method would be only called on the Job as the last method... but it could be hard to ensure that all ItemGroupMixin's respect the calling of onCopyComplete contract hence this approach seems better to me for that reason
-
由 Stephen Connolly 提交于
- The caller is no longer responsible as the listener is actually invoked from the method
-
由 Kohsuke Kawaguchi 提交于
-