- 10 3月, 2011 7 次提交
-
-
由 Kohsuke Kawaguchi 提交于
- Pass TaskListener to enable listeners to report what they are doing - Added another callback to report a failure
-
由 Tom Rini 提交于
These changes allow for a Node to check configuration values and potentially veto bringing up a Node that is otherwise in demand. For example the Lab Manager plugin could be extended to allow for only 5 slaves in a given cloud to be online at given time. Signed-off-by: NTom Rini <tom_rini@mentor.com>
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
- AbstractProject.getBuildingUpstream/getBuildingDownstream() should be symmetric. - It's unlikely for us to add another category of items, so reverted getUnblockedItems() implementation to the older one that was more efficient. - ItemList was meant to be internal, so keep it as such, at least for now.
-
由 Robert Elliot 提交于
Changed logic to build list of unblocked items in the queue safely so it will not break if a new category of queue items is added
-
由 Robert Elliot 提交于
[FIXED JENKINS-8929] Changed the definition of a building downstream project to one that is Building, Waiting, Pending or Buildable but NOT blocked. This prevents the deadlock condition where upstream project A is blocked on downstream project B, which is blocked on upstream project A - now in this scenario B will remain blocked but A will build, eventually freeing up B.
-
由 Kohsuke Kawaguchi 提交于
-
- 09 3月, 2011 5 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 alanharder 提交于
items, which upgrades the versions used for maven-hpi-plugin, maven-stapler-plugin and maven-localizer-plugin
-
由 alanharder 提交于
-
- 08 3月, 2011 1 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
- 07 3月, 2011 8 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Kohsuke Kawaguchi 提交于
-
由 Olivier Lamy 提交于
upgrade to maven 3.0.3 (will prevent issue when pom parsing phase : http://jira.codehaus.org/browse/MNG-4963)
-
- 06 3月, 2011 6 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 Olivier Lamy 提交于
-
由 Olivier Lamy 提交于
-
由 Olivier Lamy 提交于
-
由 Olivier Lamy 提交于
-
由 Olivier Lamy 提交于
take care about using settings from the remote node
-
- 05 3月, 2011 1 次提交
-
-
由 Andrew Bayer 提交于
If you had two clouds and only the second one could provision a label, it'd never get that far - check to see if a cloud can provision a label before trying to do so.
-
- 04 3月, 2011 4 次提交
-
-
由 alanharder 提交于
-
由 alanharder 提交于
-
由 alanharder 提交于
-
由 alanharder 提交于
-
- 03 3月, 2011 5 次提交
-
-
由 Kohsuke Kawaguchi 提交于
-
由 alanharder 提交于
-
由 alanharder 提交于
-
由 alanharder 提交于
-
由 alanharder 提交于
-
- 02 3月, 2011 3 次提交
-
-
由 Kohsuke Kawaguchi 提交于
I wasn't initially planning to do this, but it turns out more people needed this feature than I thought. I left the text as is, but defined a mechanism to override this in the plugin, in a possibly context sensitive way. For example, a plugin can replace this text on a job-by-job basis, or by looking at some property/builder/etc.
-
由 Kohsuke Kawaguchi 提交于
-
由 Stuart McCulloch 提交于
-