[Buildbot-devel] Responsible user for triggered build

Patrick Valsecchi pvalsecc at cisco.com
Fri Apr 4 12:17:41 UTC 2014


After a lot of fiddling, I found the source of my problem and a workaround.

The source is that the two builders are using two separate repositories 
and two separate branches, so I had this weird idea to override the 
sourceStamp. But that voids the warranty (at least stops buildbot 
passing the responsible user info, since it's part of the sourceStamp).

The work around is not to set the sourceStamp in the Trigger, but 
override the revision on the Triggerable side by setting 
alwaysUseLatest=True and branch='unittest' in the Git checkout step. 
That let the build have the correct info and have the correct revision 
to be checked out.

Thanks everybody for your suggestions.

On 02. 04. 14 09:05, Patrick Valsecchi wrote:
> Hi,
> I'm using buildbot 0.8.8 and I have a Trigger set with a Triggerable
> scheduler that goes with it. Everything works fine apart from the fact
> that the "responsible user" is not forwarded to the Triggerable scheduler.
> Is it a feature or a bug? Is there a trick to work around that?
> Thanks.
> ------------------------------------------------------------------------------
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list