ShelonCooper has quit [Remote host closed the connection]
ShelonCooper has joined #buildbot
DiJuMx has joined #buildbot
mns has quit [Ping timeout: 276 seconds]
mns has joined #buildbot
Guest6181 is now known as mjw
tflink_ has joined #buildbot
dustinm`_ has joined #buildbot
Humbedoo` has joined #buildbot
cmouse_ has joined #buildbot
tflink has quit [*.net *.split]
dustinm` has quit [*.net *.split]
Humbedooh has quit [*.net *.split]
cmouse has quit [*.net *.split]
Humbedoo` is now known as Humbedooh
Humbedooh has quit [Changing host]
Humbedooh has joined #buildbot
fabian has joined #buildbot
fabian has left #buildbot [#buildbot]
fabianj has joined #buildbot
<fabianj>
Hello. Does anyone here have any idea how to parameterize a force scheduler with a user using the REST API? Similar to how a commit author is referenced under "Responsible Users" (owners: ["Max Mustermann <max@mustermann.net>"]). I've tried various keys and formatted values, but both owner and owners are empty.
fabianj has quit [Quit: Client closed]
fabianj has joined #buildbot
fabianj has quit [Client Quit]
mjw is now known as Guest825
Guest825 has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
Guest825 has joined #buildbot
Evilham11 has quit [Remote host closed the connection]
Evilham has joined #buildbot
flavius-as has joined #buildbot
<flavius-as>
hi
<flavius-as>
Would there be a need for dynamically adding latent docker workers from a repo, but custom built images on top of the base docker image for buildbot? the idea is to put the repo in control of the whole process, intertwine steps, various images potentially, and still have it as an opt-in way of working, meaning nothing is hard coded on the master
<flavius-as>
it would be obvious just for trusted repositories. I got some things to work, but generally I feel like I'll need to tweak buildbot by making deeper cuts
<flavius-as>
obviously I could monkey patch, fork, etc. But I am wondering if there have been or are efforts on this front, previous discussions already discarded, etc that I could refer to
<flavius-as>
also I felt like a more interactive discussion could be more productive at this stage than writing to the mailing list. and the mailing list seems quite dead
<flavius-as>
would appreciate some knowledgeable views on this or maybe I didn't explain too clear what I want to accomplish
Evilham1 has joined #buildbot
Evilham has quit [Ping timeout: 276 seconds]
Evilham1 has quit [Ping timeout: 244 seconds]
<flavius-as>
kind of like this https://github.com/buildbot/buildbot_travis but the configuration is more buildbot like (python code) and not so much Travis like (yaml or whatever)
Evilham1 has joined #buildbot
<flavius-as>
I just found that discussions on github seem active. also some unanswered threads about leveraging the strengths of buildbot while also having workflows leaning onto jenkins pipelines
<flavius-as>
this seems to align roughly to what I have, however what bothers me is the lack of replies in those discussions. what I mean is: I'd might like to make such a project but I need to know that it's a welcome addition and not something ultimately rejected