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.

Jelly/Groovy views don't do this, but erb views from Ruby often do it,
so better be robust. This is breaking J-on-J currently.

At least now the back button won't trigger the drop-down notification.

It was formerly on <LI> but now it's on <A> as we now allow bare <A>s to
have context menus.

1. you hover over the <a> tag
2. context menu displays
3. you try to move the mouse over to the menu
4. menu disappears
5. you can't click the menu *frustration*

This hopefully avoids showing menus when the user didn't intend to see
them

In this change, I've added it to various links in the list view to get
the sense of how it feels like.

So that parameter definitions can define optional parameters.

(and replaced custom event addition with simpler one from Prototype)

[FIXED JENKINS-12302] Refactor anonymout class for loading groovy script into separate class as static block (due to inheritance of outer class from CLICommand) initialization leads to NPE (namely in Jenkins.getInstance Jenkins.getInstance().getPluginManager())

On iptables protected system, full time out can take 30 secs, which is
too long.