- Jul 06, 2013
-
-
Kohsuke Kawaguchi authored
Conflicts: core/src/main/java/hudson/model/AbstractProject.java
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
This helps a lot when mocking AbstractProject in unit tests, because so I don't have to suppress the constructor with PowerMockito
-
Christoph Kutzinski authored
-
Christoph Kutzinski authored
[JENKINS-14585] core side fix for: claim-plugin cannot claim broken tests in maven jobs
-
ssogabe authored
-
- Jul 05, 2013
-
-
Kohsuke Kawaguchi authored
-
- Jul 04, 2013
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
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 authored
-
Nicolas De Loof authored
-
Nicolas De Loof authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
(cherry picked from commit d8f74cf8)
-
- Jul 03, 2013
-
-
Kohsuke Kawaguchi authored
-
Christoph Kutzinski authored
-
Stephen Connolly authored
If every node is restricted to tied jobs only, Matrix build jobs can never start
-
Stephen Connolly authored
-
Stephen Connolly authored
- 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 authored
- The caller is no longer responsible as the listener is actually invoked from the method
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
Use DescribableList to handle the copy-on-write semantics correctly. The vector class just doesn't cut it, and we've been setting a new value to this field, which will violates all sorts of the concurrent programming practice. This change has the nice side effect of removing {{class="vector"}} from the persisted XML. A test is added to make sure we can still read back such an XML.
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
- Jul 02, 2013
-
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Seiji Sogabe authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
-
Kohsuke Kawaguchi authored
Revisiting the fix. Avoid parsing the entire text by only looking at the tail portion.
-
Kohsuke Kawaguchi authored
This will hopefully reduce the file locking problems on Windows.
-