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: Tom Rini <tom_rini@mentor.com>
- 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.
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.
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.
${param}
param = http://host/job/foo/14
If you just wanted the name ('foo') or the number (14) as an expansion,
you're forced to re-tokenise it somehwere else such as a script.
Add 2 extra environment vars:
param.jobName = foo
param.number = 14
Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
Ant build step had quite a mix: buildFile and antOpts expanded against
env, properties against buildVariables, and targets against both.
Now merging buildVariables into env and applying to all.
I added a mode where one can launch a child process without the built-in pumping support, making it trivial to read until EOF in the distributed environments.
This concludes the fix.
I did a checkout for our internal fork of JmDNS [1] and the
upstream version [2] to compare what the differences were..
I found none. There do not appear to be any local edits to
our fork so I can not figure out why we did the fork to
begin with.
Perhaps some older version had locally patched bugs which
have since been resolved? Anyhow, given that JENKINS-8647
is causing lots of people lots of grief, and it is enabled
by default, I went ahead and bumped to jmdns-3.4.0 upstream.
I think reduction of forks for library projects is generally
good, and especially when we have no practical changes made
to our version.
[1] https://github.com/jenkinsci/jmdns
[2] https://jmdns.svn.sourceforge.net/svnroot/jmdns/tags/JmDNS_3_2_1/