Hudson can now remotely install JDK on Windows slaves when connecting via the
"Let Hudson control this Windows slave as a Windows service" mode.
<li class=rfe>
The "Let Hudson control this Windows slave as a Windows service" mode now allows the same Windows slave
to be used by multiple Hudson masters.
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32525 71c3de6d-444a-0410-be80-ed276b4c234a
module builds too.. this avoids orphaned module builds that then get looked at
in determining the overall result for the prior ModuleSetBuild.. possibly
mysteriously changing the displayed result for that prior build, with no visual
indication as to why (this part just fixed in r32410.. build page will now list
all module builds, so you can see/delete the orphaned module build).
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32411 71c3de6d-444a-0410-be80-ed276b4c234a
contrary to comment in this jelly.. you can trigger a build of an individual
module from hudson UI. Refactor this jelly to use the current style most
of the time, and the multi-build style whenever needed.
This will help those affected by HUDSON-6779 as the orphaned builds will
now be visible on the build page, so you can click on and then delete them.
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32410 71c3de6d-444a-0410-be80-ed276b4c234a
but jelly does get AbstractMethod error (not null) if instance doesn't implement the
canDelete method, so I'll just release a new version of nested view plugin..
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32398 71c3de6d-444a-0410-be80-ed276b4c234a
https://svn.dev.java.net/svn/hudson/branches/rc
........
r32297 | kohsuke | 2010-06-25 17:34:56 -0700 (Fri, 25 Jun 2010) | 1 line
[maven-release-plugin] prepare release hudson-1_364
........
r32299 | kohsuke | 2010-06-25 17:35:15 -0700 (Fri, 25 Jun 2010) | 1 line
[maven-release-plugin] prepare for next development iteration
........
r32305 | kohsuke | 2010-06-25 21:37:44 -0700 (Fri, 25 Jun 2010) | 1 line
updated changelog as a part of the release
........
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32326 71c3de6d-444a-0410-be80-ed276b4c234a
user-private views. Use it="${app}" for Manage Hudson and New Job links,
so these check the proper permission. Replaced !it.isDefault() check
with new ViewGroup.canDelete API call.. Hudson ViewGroup uses isDefault()
for this method; MyViewsProperty checks views.size() > 1 so link is
hidden when there is only one user-private view.
Used !=false in jelly for backward compatibility (if a plugin implements
ViewGroup but does not have canDelete, null!=false will result in true).
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32319 71c3de6d-444a-0410-be80-ed276b4c234a
Go to getDescriptorByName rather than getDescriptor to get the help files. This is useful in
situations where Hudson instance is not the root of the webapp.
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32272 71c3de6d-444a-0410-be80-ed276b4c234a
- Task X becomes buildable
- Thread E1 enters the pop() method, assigns X to an executor E2.
Note that at this point X is not removed from the buildables list yet
- Thread E1 goes to offer.event.block and blocks, losing the lock
- Thread E3 enters the pop() method, assigns X to anogher executor E4.
This is possible because X is still in the buildables list.
- Thread E3 goes to offer.event.block and blocks, losing the lock.
- Thread E2 wakes up, obtains the lock and execute the rest of the
pop() method. It decides that it's assigned X, it removes X from
the buildables list.
- Thread E2 leaves the pop() method, loses the lock, and starts building X
- Thread E4 wakes up, obtains the lock, and executes the rest of the
pop() method. It decides that it's assigned X. It tries to remove X
from the buildables list. This remove operation becomes no-op,
but we don't check that.
- Thread E4 leaves the pop(), and start building X.
Thus we end up building X twice.
To avoid this problem, I've introduced the 4th state "pending", and moves BuildableItem from buildables to pendings as soon as we assigned it to the executor. New BuildableItem cannot be created
while its another copy is either in the buildables or pendings state.
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32258 71c3de6d-444a-0410-be80-ed276b4c234a
Given the use case described in the bug, I wonder if it's better to have a different extension point (sort of like ComputerListener) that can contribute build variables to any builds going on in the system.
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@32257 71c3de6d-444a-0410-be80-ed276b4c234a