[Buildbot-commits] [Buildbot] #2218: Add support for declarative configuration.

Buildbot nobody at buildbot.net
Sun Feb 10 23:19:13 UTC 2013


#2218: Add support for declarative configuration.
-------------------------+--------------------
Reporter:  tom.prince    |       Owner:
    Type:  project-idea  |      Status:  new
Priority:  major         |   Milestone:  1.0.+
 Version:  0.8.5         |  Resolution:
Keywords:  config        |
-------------------------+--------------------
Changes (by dustin):

 * type:  enhancement => project-idea


Old description:

> <@exarkun> That's why you also have plugins│
> <@exarkun> It's just about actually separating your code from your
> configuration
> <@exarkun> Your wacky auto-generated list of slave settings is fine, but
> put it in a module, unit test it (hey, document it!  distribute it!)
> <@exarkun> and then in your _configuration_ say "and please use wacky
> auto-generate slave plugin"

New description:

 Buildbot's configuration has historically been a Python file that Buildbot
 executes.  The result of that execution is then used to set up the master.
 This assumes users can write valid Python code, and encourages people to
 do all manner of fragile or non-maintainable things.  See #2218 for more.

 == scope ==
 This project will involve some careful thought about how users interact
 with Buildbot, and how we can maintain backward compatibility while
 providing users with a forward migration path.  Once that's complete, the
 modifications to the code will be fairly minimal, and mostly limited to
 `master/buildbot/config.py` (with associated tests).  However, the change
 will require alteration -- a rewrite, really -- of the entire
 "Configuration" section of the manual; this will be the most time-
 consuming (but critical) part of this project.

 == examples ==
 -
 http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit
 .org-config/config.json

--

Comment:

 Previous description:
 ----
 {{{
 <@exarkun> That's why you also have plugins│
 <@exarkun> It's just about actually separating your code from your
 configuration
 <@exarkun> Your wacky auto-generated list of slave settings is fine, but
 put it in a module, unit test it (hey, document it!  distribute it!)
 <@exarkun> and then in your _configuration_ say "and please use wacky
 auto-generate slave plugin"
 }}}

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2218#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the Commits mailing list