[Buildbot-devel] try command options code questions

[Doug Latornell]

On Wed, Mar 30, 2011 at 1:44 PM, Tom Prince <tom.prince at ualberta.net> wrote:
> On 2011-03-30, Doug Latornell wrote:
>> I'm finally getting some time in on trying to clean up the buildbot
>> try command line options and their .buildbot/options file
>> counterparts.
>
> I was looking at something related recently. I wrote some code
> https://github.com/tomprince/buildbot/tree/try-repo
> recently to allow passing a repository option to try. I also looked and
> adding smarts to detect the correct git repository to use.
> https://github.com/tomprince/buildbot/tree/try-repo-hack
>
> The issue that I ran into is that there are to views one can take with a
> DVCS (in particular git). On can talk about local branches, or local
> names for remote branches, and local names for remote repositories. But
> one can also talk about remote branches and remote repositories
> directly.
> ...

I hadn't thought about the implication of DCVS for try. I'm not really
using try for it's intended purpose, but rather as a sort of side-door
to trigger a group of special build that need to be run from time to
time to produce reference data files for the regular builds.

The itch I set out to scratch arises from the fact that I started
running the buildmaster in a virtualenv. If I issue a buildbot try
command via ssh I need to specify the buildbot executable to be used.
So, I want something similar to the hg --remotecmd option. I had
thought of calling it --remotecmd too, but perhaps something like
--buildbotbin would be more appropriate. Anyway, when I proposed it to
this list a few month ago, Dustin came back with the challenge to make
the try options more consistent, and improve their documentation, and
I decided to take that on while I was at it. So, that's what I'm
working on in my
https://github.com/douglatornell/buildbot/tree/tryfixes branch.

Doug