[Buildbot-devel] Triggering dependent builds of unrelated SCM

[Bob Hood]

I've set up a Triggerable set of builders for a project that is dependent on
the successful completion of a different build.  This build contains libraries
that the secondary build requires, so it must build first, and then the
secondary product can attempt to build afterward.

Unfortunately, it looks like I cannot do this sort of cascading build, because
the Triggerable type uses the same SCM revision from the first build in order
to check out the SCM of the second.  These are two independent projects, at
least independent in the fact that they are being managed by two separate
entities in two separate SCM systems (the first is Subversion, the second is
git).  They therefore have two different revisions.

Can I somehow tell the Triggerable system to just do a "force build" or "build
head" on the triggered lane instead of having it try to use the revision from
the first build on the check-out of the second?  The documentation on this
type of Scheduler in 0.8.3 suggests nothing.


Render me gone,                       |||
Bob                                 ^(===)^
---------------------------------oOO--(_)--OOo---------------------------------
   "One of the penalties for refusing to participate in politics is that you
           end up being governed by your inferiors." -- /Plato/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20111024/d6add60b/attachment.html>