<tardyp>
This will help maintain our metabuildbot GCP project costs and maintain our HW for buildbot.net infrastructure
<tardyp>
thanks a lot this is very much appreciated
<tardyp>
another very well apreciated donation is just contributing to the code and issues :)
<flx[m]>
thanks to you too :)
<flx[m]>
I there a reason why the donation link is not mentioned anywhere?
<tardyp>
Well, if we had too much donation, we wouldn't really be able to spend it. so I guess this is why
<tardyp>
the sparse ressource is more development power. changing $ into buildbot development work is not that simple
<cmouse>
it would be better if there was some oss development support trurst =)
<cmouse>
which would accept donations and support oss projects approriately.
<tardyp>
.. scarse resource
<flx[m]>
tardyp: yeah, I know. oss developers are always missing.
<flx[m]>
I am setting up a buildbot instance for my organization and we want to link it to Keycloak OAuth2, maybe even OpenID Connect since it depends on OAuth2. I think it shouldn't be that much work, but that is definitely planned to contribute :)
<flx[m]>
tardyp: have you thought about attending gsoc?
<flx[m]>
it's a great possibility to get new developers into a project
<cmouse>
we authenticate users with that, and pass the user as X-Remote-User to bb, then you can use ldap as user information provider source.
<flx[m]>
well, we don't have an ldap running
<cmouse>
do you get the same information from your oauth2?
<tardyp>
buildbot already has some oauth support, it should be easy to add more. oauth2 proxy is a bit more secure though as it prevents unauthenticated users to access the ui
<cmouse>
actually i lied, we don't use ldap
<cmouse>
i thought we did
<cmouse>
seems we only have the x-remote-user header thingy
<flx[m]>
unauthenticated users should see the UI, that's fine. they just shouldn't be able to do anything with it (like stopping or starting jobs)