#993: Expose category information in a structured way
------------------------+-------------------------
Reporter: exarkun | Owner: jaredgrubb
Type: enhancement | Status: assigned
Priority: minor | Milestone: 0.9.0
Version: 0.8.1 | Resolution:
Keywords: |
------------------------+-------------------------
Changes (by dustin):
* owner: => jaredgrubb
* status: new => assigned
Old description:
> Builders can have a category ([ticket:928 maybe multiple categories in
> the future]). Twisted uses this to segregate builders into those for
> supported platforms (which we always keep green) and those for
> unsupported platforms (which we try to improve but can be red).
>
> The categories are defined in the master config, where they can't really
> be extracted by other tools (and certainly the information isn't
> available remotely). It informs certain views (ie, html generation),
> which indirectly reveals the categories. But the information can't be
> worked with in this form without scraping html.
>
> It would be great if there were a way to get this information in a
> structured way. For example, an XML-RPC call which accepts a builder
> name and returns a category (there's already an XML-RPC call that returns
> all builder names). Or perhaps an XML-RPC call like the existing
> `getAllBuilders` but the response to which includes more information per
> builder than just the name.
>
> This would let external tools interact with buildbot more easily and with
> less duplication of configuration (for example, the build forcing tool
> Twisted uses, which triggers a build on all "supported" category
> builders, which currently keeps a copy of the list of builders which are
> in that category).
New description:
Builders can have a category ([ticket:928 maybe multiple categories in the
future]). Twisted uses this to segregate builders into those for
supported platforms (which we always keep green) and those for unsupported
platforms (which we try to improve but can be red).
The categories are defined in the master config, where they can't really
be extracted by other tools (and certainly the information isn't available
remotely). It informs certain views (ie, html generation), which
indirectly reveals the categories. But the information can't be worked
with in this form without scraping html.
It would be great if there were a way to get this information in a
structured way. For example, an XML-RPC call which accepts a builder name
and returns a category (there's already an XML-RPC call that returns all
builder names). Or perhaps an XML-RPC call like the existing
`getAllBuilders` but the response to which includes more information per
builder than just the name.
This would let external tools interact with buildbot more easily and with
less duplication of configuration (for example, the build forcing tool
Twisted uses, which triggers a build on all "supported" category builders,
which currently keeps a copy of the list of builders which are in that
category).
--
--
Ticket URL: <http://trac.buildbot.net/ticket/993#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
