#1894: phase out use of the BuildRequest class
------------------------+-------------------
Reporter: dustin | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.9.+
Version: master | Keywords:
------------------------+-------------------
Constructing a !BuildRequest involves a lot of database queries, and in
most cases is unnecessary. However, it is part of the specification of
the {{{nextBuild}}} and {{{mergeRequest}}} configuration parameters, and
is also used internally by the build-initiation code.
Let's find a way to change both of these uses so that the class can simply
disappear. Fixing the build machinery is easy. And we can probably add a
wrapper or decorator that will make the old {{{nextBuild}}} and
{{{mergeRequest}}} functions work with a new, !BuildRequest-free API, so
users would only need to add the wrapper or decorator to their
configuration when upgrading (albiet with a signficant performance
penalty).
--
Ticket URL: <http://trac.buildbot.net/ticket/1894>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
