done with post-production (as opposed to just done with build steps). Jobs
that had long running tasks that occured in their post-production state, i.e.,
build wrappers, post-build steps, could get into the situation where a queued
build would start running on an executor while the previous build was still
running post-build actions. If the two executors shared the same workspace,
the new build could delete information with a clean that the current build
still needed for processing.
- Changed AbstractProject.getCauseOfBlockage() to call isLogUpdated instead
of isBuilding.
core/src/main/java/hudson/model/AbstractProject.java
- Added isLogUpdated.
core/src/main/java/hudson/model/Job.java
- Added test case.
test/src/test/java/hudson/model/JobQueueTest.java
- Change log
changelog.html
Repository on our domain name would allow us to control redirection
better.
maven.glassfish.org being down makes this issue a higher priority.
This is a permanent change --- even if m.g.o is back we won't be
going back.
The motivation of this is to enable test code to inject components from Jenkins, which means we need a single Injector that can see all of those, including @TestExtension and regular @Extension. Then I realized that the current implementation is broken, as it creates two independent Injectors. This has other undesirable side effects like @TestExtension components not being able to inject @Extensions, etc.
I briefly experimented with hierarchical Injectors (where we first create Injector that loads @Extension then create another that loads @TestExtension as a child), but this was hard to get right as we have no control over which ExtensionFinder gets instantiated first --- we'd be at the mercy of SezPoz.
So the eventual approach is to allow a single GuiceFinder to recognize multiple annotations. This also works well with our using child injector for installing plugins without restart