[Buildbot-devel] Looking for suggestions (TrySchedulers - Buildbot 0.9)

[Francesco Di Mizio]

Hello there,

in the past at the company I was working for we used to have a buildbot
based system mainly used for CL validation (making sure it compiles before
checking it in).

This was based on a minimalistic webpage that would in turn call some
buildbot python api to a add a change to BB (it might have been
addSourceStamp) so that it would show up on the left side of the waterfall.
The schedulers being used were AnyBranchSchedulers. Without a successful
'test' a p4 trigger would prevent you from checking in.

That approach can somehow be compared to
https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/master/try_job_base.py

I've then noticed that Buildbot comes with TrySchedulers. I am now in the
middle of setting up something very similar to what I described above and
was wondering if I can get away with it by using TrySchdulers.

As far as I understand by reading the docs, a developer needs to run
'buildbot try', which I'd assume requires buildbot to be set up on their
machine, which is a requirement I would like to avoid. Please correct me if
I am wrong.

Also I've been following http://nine.buildbot.net/#/ with interest. Since
it's going to take a while to set all up, can it make sense for me to start
off with 0.9 directly?

Cheers,
 Francesco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20150116/4539f194/attachment.html>