[Buildbot-devel] Building source tarballs from git and then building those in dependent builders?

[James Youngman]

On Tue, May 5, 2009 at 2:17 AM, Doug Latornell <doug at sadahome.ca> wrote:

> I have a situation somewhat similar to this.  In my case one of the
> compilers we use is only licensed on one of the slaves.  I build the
> executable on that slave then use a Trigger step to launch another
> build on a different slave via a Triggerable scheduler.

So far, straightforward and documented in the manual.

> That build
> starts by copying the executable file from the compile-slave's working
> directory into its own working directory, then runs the tests.  I use
> a ShellCommand step to copy the executable because my slaves share
> common storage.  I'm sure that you could do the same in the NFS case,
> and a ShellCommand that used scp could probably handle this across the
> network (I haven't tried that tough).

Does the Trigge step also propagate the accompanying list of changes
(if my downstream builders now can't build from the source tarball, it
likely has something to do with the source code changes in the
repository)?   Would you be able to share your master.cfg file (well,
the relevant parts of it, I don't need to know the names or passwords
of the build slaves)?

Thanks,
James.