#2152: Let forced build properties override all others
-----------------------+------------------------
Reporter: brendan | Owner:
Type: defect | Status: closed
Priority: minor | Milestone: undecided
Version: 0.8.5 | Resolution: wontfix
Keywords: properties |
-----------------------+------------------------
Changes (by dustin):
* status: new => closed
* resolution: => wontfix
Comment:
As tomprince mentioned in channel, this is because slave parameters
override scheduler parameters -- see
http://buildbot.net/buildbot/docs/latest/manual/cfg-
properties.html#properties
With the !ForceScheduler changes that are about to land
(https://github.com/buildbot/buildbot/pull/278), this will seem more
sensible, since the builds will be triggered by the force scheduler. In
other words, this is by design and expected behavior.
You'll need to work around this with your properties. We did add the
ability to use properties in a Properties(default=..):
https://github.com/buildbot/buildbot/commit/54728899517a134f6b3678fcd038c796f51072d5
--
Ticket URL: <http://trac.buildbot.net/ticket/2152#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
