[users at bb.net] Programmatically triggering forced schedulers

Pierre Tardy tardyp at gmail.com
Sun Feb 12 18:39:18 UTC 2017

Hi Eliot,

Buildbot uses cookies to authorize a REST api request if the authentication
scheme is Oauth2.
There is at the moment no other way to authenticate.
Probably this would be handy to have access token generation for us with

With Buildbot 0.9.4 there is a new JWT implementation which is similar to
access token.
The JWT is signed with a secret key unique to the buildbot cluster, and is
valid for 1 week (you can raise this value)

So if you want a quick hack, you can just dump you cookie from your
browser, and use that in scripts.
If you need a cleaner way, you would need to add some UI and REST api in
Buildbot to generate JWT token for scripts, with longer expiration date.

Le dim. 12 févr. 2017 à 09:40, Elliot Saba <staticfloat at gmail.com> a écrit :

> Hello there,
> I want to programmatically trigger some forced schedulers in my buildbot,
> and I'm not sure what the easiest way to do that is.  I want to trigger
> builds on multiple forced schedulers, with parameters (such as the revision
> to build) from an external tool.  I've considered using the REST api, but
> because I'm using GitHub OAuth2 authentication, this is more complex than I
> had originally anticipated.  Is there a way to have multiple authentication
> methods available?  Can I, for example, disable authentication if the
> request is coming from `localhost` or something similar?
> Thanks,
> -E
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170212/c64bfbc9/attachment.html>

More information about the users mailing list