For example trigger a builder for changes affecting files under arrow/ci which reloads the builder object within the build master's process. We are not limited to shell commands, arbitrary python functions can be executed too, but the semantics would be similar to running MasterShellCommand [1].
[1]: http://docs.buildbot.net/2.4.0/manual/configuration/buildsteps.html#running-commands-on-the-master On Thu, Sep 5, 2019 at 3:17 PM Antoine Pitrou <anto...@python.org> wrote: > > Le 05/09/2019 à 15:04, Krisztián Szűcs a écrit : > >> > >> If going with buildbot, this means that the various build steps need to > >> be generic like in Travis-CI (e.g. "install", "setup", "before-test", > >> "test", "after-test"...) and their contents expressed outside of the > >> buildmaster configuration per se. > >> > > This is partially resolved with the Builder abstraction, see an example > > here [1]. We just need to add and reload these Builder configurations > > dynamically on certain events, like when someone changes a builder > > from a PR. > > This is inside the buildmaster process, right? I don't understand how > you plan to change those dynamically without affecting all concurrent > builds. > > Regards > > Antoine. >
