[Buildbot-devel] Changing the master config dynamically

[Karoly Kamaras]

I tried it this morning with a basic setup, and i managed to

1) add a new build step to a builder while it was running
2) add new triggerable scheduler and builder to an existing config

In both cases the actual build went on and finished, and it used the new
config in the following builds. However it might need a more complex
workaround because a change in the config would affect the current build as
well even if it's not finished yet. In this case i think it's not
Buildbot's reponsibility anymore to handle current and future jobs with the
different config (i'm just thinking loudly here).

Here is my example:

BUILDER1 triggers
Builder1A,
Builder1B,
Builder1C in this order.

I start BUILDER1 and while Builder1A is running, i change the config of
Builder1B. I would like the current build to finish 1A, 1B and 1C with the
original config, but after that start the whole flow over again with the
new config of 1B.

Now i'm not sure if it's a valid use-case, maybe i overcomplicated things,
but the original problem: "is it possible to reconfig without restart"
seems to be solved. At least for a fairly simple configuration, adding
steps, builders and schedulers seems to be working. The whole job-flow
handling should be my concern.

Thanks,



*Karoly Kamaras*
Developer at Prezi <http://prezi.com>

On Thu, Oct 9, 2014 at 12:20 PM, Mikhail Sobolev <mss at mawhrin.net> wrote:

> Hi Karoly,
>
> On Wed, Oct 08, 2014 at 10:55:50PM +0200, Karoly Kamaras wrote:
> > Thank you all for the quick replies.
> Too quick, it seems :)
>
> > @Mikhail, thanks, that was what i remembered just didn't find it. So this
> > solution would allow me to run a build while updating another builder in
> > the same configuration and start a new process while the original one
> > finishes? In our case it would mean something like this: someone pushes a
> > change, that starts building module A, and in the same team someone else
> > updates the build steps of module B, and updates the config (our custom
> > DSL) in their repo. By pushing it, it should reconfig the master so the
> new
> > module B steps would be live, but the module A build would continue and
> > finish without any issues.
> Now, that I read about the problem, the answer is "I am not sure".
>
> What I suggested is the way to make sure that the latest versions are
> used for `buildbot reconfig`.  I am not sure whether the running builds
> will continue to run etc.
>
> --
> Misha
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20141009/b2839691/attachment.html>