On Fri, Sep 6, 2019 at 12:15 PM Antoine Pitrou <anto...@python.org> wrote:
> > Le 06/09/2019 à 12:13, Krisztián Szűcs a écrit : > > On Fri, Sep 6, 2019 at 12:01 PM Antoine Pitrou <anto...@python.org> > wrote: > > > >> > >> Le 06/09/2019 à 10:07, Krisztián Szűcs a écrit : > >>> For example trigger a builder for changes affecting files under > arrow/ci > >>> which reloads the builder object within the build master's process. > >> > >> I am asking you how this affects only the current build and not other > >> concurrent builds. > > > > We need to register the changed builders as new ones with a corresponding > > triggerable scheduler, and trigger them. > > Don't you still need to restart the buildmaster to see those new builders? > Nope. > > I get the impression that it is a complicated and fragile solution to > the problem. > Ursabot has a bunch of tests to ensure that we don't brake any of the functionality, so fragility can be avoided by testing it. There might be easier solutions, like spinning up another master, but choosing the right way to do it requires some experimenting. > > Regards > > Antoine. >
