From jolly_roger at itblog.org.ua  Mon Jun  1 05:56:36 2020
From: jolly_roger at itblog.org.ua (Andrii Senkovych)
Date: Mon, 1 Jun 2020 08:56:36 +0300
Subject: [devel@bb.net] Tracking state of multiple latent workers
Message-ID: <CAMS_SF+=+KBhM7sfXDH2jiwKPMU2d4BuA-dH+bY57r=BWir_Gw@mail.gmail.com>

Hi Buildbot users,

I'm looking for a way to run multiple latent workers that all depend
on a single gateway and currently I'm looking for a way to start the
gateway before any latent worker is provisioned and destroy it after
all latent workers are stopped.

So far I have ended up using terraform to start and provision both
gateway and worker in one run. However in order to use multiple
workers I need to have some kind of state to know what workers have
been started already and pass the list of workers to terraform (for
example as environment variable) so when a list includes new names,
workers are being created (the opposite is true: if the list misses
some workers that previously existed, they should be destroyed).

Please advise how to implement this with Buildbot.

Thank you.

--
Best regards,
Andrii Senkovych

From povilas at radix.lt  Mon Jun  1 19:27:59 2020
From: povilas at radix.lt (Povilas Kanapickas)
Date: Mon, 1 Jun 2020 22:27:59 +0300
Subject: [devel@bb.net] Tracking state of multiple latent workers
In-Reply-To: <CAMS_SF+=+KBhM7sfXDH2jiwKPMU2d4BuA-dH+bY57r=BWir_Gw@mail.gmail.com>
References: <CAMS_SF+=+KBhM7sfXDH2jiwKPMU2d4BuA-dH+bY57r=BWir_Gw@mail.gmail.com>
Message-ID: <79143f06-b1c5-3e2b-4632-4d45480db079@radix.lt>

Hi Andrii,

On 6/1/20 8:56 AM, Andrii Senkovych wrote:
> Hi Buildbot users,
> 
> I'm looking for a way to run multiple latent workers that all depend
> on a single gateway and currently I'm looking for a way to start the
> gateway before any latent worker is provisioned and destroy it after
> all latent workers are stopped.
> 
> So far I have ended up using terraform to start and provision both
> gateway and worker in one run. However in order to use multiple
> workers I need to have some kind of state to know what workers have
> been started already and pass the list of workers to terraform (for
> example as environment variable) so when a list includes new names,
> workers are being created (the opposite is true: if the list misses
> some workers that previously existed, they should be destroyed).

There's a very similar concept already almost implemented called
Machine. A latent worker can have a Machine attached to it and it will
always try to wake the machine when starting up (if it's not already
started) and shutdown it when there are no latent workers that use the
machine.

I think this concept is very similar to your use case.

I have some code already written that suspends and wakes up a local
machine with many workers on demand so that it doesn't burn electricity
needlessly. I need to polish this code and do a pull request.

Regards,
Povilas

> --
> Best regards,
> Andrii Senkovych
> _______________________________________________
> devel mailing list
> devel at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/devel
> 

From jolly_roger at itblog.org.ua  Mon Jun  1 20:07:43 2020
From: jolly_roger at itblog.org.ua (Andrii Senkovych)
Date: Mon, 1 Jun 2020 23:07:43 +0300
Subject: [devel@bb.net] Tracking state of multiple latent workers
In-Reply-To: <79143f06-b1c5-3e2b-4632-4d45480db079@radix.lt>
References: <CAMS_SF+=+KBhM7sfXDH2jiwKPMU2d4BuA-dH+bY57r=BWir_Gw@mail.gmail.com>
 <79143f06-b1c5-3e2b-4632-4d45480db079@radix.lt>
Message-ID: <CAMS_SFJhv4sac4iUdoksxb9rY-2UGAx5+8OQy2Lz+=+gQ5ccuw@mail.gmail.com>

Hi Povilas,

Thanks for the info, I'll surely have a look on it. But it seems for
my case it will be sufficient to have a step that can query Data API
and put a list of workers into a Property for future use. Do you
perhaps know how to do this? I've used Buildbot in times of 0.8.x and
now struggling a bit with the new features.

Thank you.

-- 
Best regards,
Andrii Senkovych

??, 1 ????. 2020 ? 22:28 Povilas Kanapickas <povilas at radix.lt> ????:
>
> Hi Andrii,
>
> On 6/1/20 8:56 AM, Andrii Senkovych wrote:
> > Hi Buildbot users,
> >
> > I'm looking for a way to run multiple latent workers that all depend
> > on a single gateway and currently I'm looking for a way to start the
> > gateway before any latent worker is provisioned and destroy it after
> > all latent workers are stopped.
> >
> > So far I have ended up using terraform to start and provision both
> > gateway and worker in one run. However in order to use multiple
> > workers I need to have some kind of state to know what workers have
> > been started already and pass the list of workers to terraform (for
> > example as environment variable) so when a list includes new names,
> > workers are being created (the opposite is true: if the list misses
> > some workers that previously existed, they should be destroyed).
>
> There's a very similar concept already almost implemented called
> Machine. A latent worker can have a Machine attached to it and it will
> always try to wake the machine when starting up (if it's not already
> started) and shutdown it when there are no latent workers that use the
> machine.
>
> I think this concept is very similar to your use case.
>
> I have some code already written that suspends and wakes up a local
> machine with many workers on demand so that it doesn't burn electricity
> needlessly. I need to polish this code and do a pull request.
>
> Regards,
> Povilas
>
> > --
> > Best regards,
> > Andrii Senkovych
> > _______________________________________________
> > devel mailing list
> > devel at buildbot.net
> > https://lists.buildbot.net/mailman/listinfo/devel
> >
> _______________________________________________
> devel mailing list
> devel at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/devel

From dustin at buildbot.net  Tue Jun  2 15:00:02 2020
From: dustin at buildbot.net (dustin at buildbot.net)
Date: Tue, 2 Jun 2020 15:00:02 GMT
Subject: [devel@bb.net] Buildbot Weekly Summary
Message-ID: <202006021500.052F02eG004232@trac.buildbot.net>

An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200602/e0f1a852/attachment.html>

From dustin at buildbot.net  Tue Jun  9 15:00:02 2020
From: dustin at buildbot.net (dustin at buildbot.net)
Date: Tue, 9 Jun 2020 15:00:02 GMT
Subject: [devel@bb.net] Buildbot Weekly Summary
Message-ID: <202006091500.059F02FV077770@trac.buildbot.net>

An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200609/613982ec/attachment.html>

From povilas at radix.lt  Sun Jun 14 15:10:53 2020
From: povilas at radix.lt (Povilas Kanapickas)
Date: Sun, 14 Jun 2020 18:10:53 +0300
Subject: [devel@bb.net] Buildbot 2.8.2
Message-ID: <4e3ca417-88b4-07b3-af3b-e08dcc3b84d0@radix.lt>

Buildbot 2.8.2 has been released!

The release notes can be found here:

http://docs.buildbot.net/2.8.2/relnotes/index.html

Happy building!

Regards,
Povilas

From dustin at buildbot.net  Tue Jun 16 15:00:02 2020
From: dustin at buildbot.net (dustin at buildbot.net)
Date: Tue, 16 Jun 2020 15:00:02 GMT
Subject: [devel@bb.net] Buildbot Weekly Summary
Message-ID: <202006161500.05GF02EU097835@trac.buildbot.net>

An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200616/b3b066c8/attachment.html>

From dustin at buildbot.net  Tue Jun 23 15:00:02 2020
From: dustin at buildbot.net (dustin at buildbot.net)
Date: Tue, 23 Jun 2020 15:00:02 GMT
Subject: [devel@bb.net] Buildbot Weekly Summary
Message-ID: <202006231500.05NF02uq064709@trac.buildbot.net>

An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200623/b3cabb22/attachment.html>

From dagofthedofg at gmail.com  Mon Jun 29 22:06:31 2020
From: dagofthedofg at gmail.com (dag dg)
Date: Mon, 29 Jun 2020 17:06:31 -0500
Subject: [devel@bb.net] Dynamically add tags to builder
Message-ID: <CAO2Qn5m0BzW2hoUL_eQcWeZFm9jbAEkgRecSizfxrqMhkP1t9w@mail.gmail.com>

Is there a way to add tags to a builder as buildbot is running and not just
during startup? I'm trying to set up builds to add a "failure" tag to their
builder if they fail, and the next build that succeeds to remove said tag.
I'm trying to do this as a workaround for the following issue:

https://github.com/buildbot/buildbot/issues/5056

I was digging into the doStepIf attribute of build steps and found I could
get a reference to the builder tags through the step object passed to the
custom doStepIf function at <step.build.builder.config.tags>. However when
I modify this value while it does get updated, the webUI does not show the
new tags so I'm obviously missing something.

The ability for my team to quickly identify build failures in the UI is
fairly important and if we would be able to use tagging this would work
well but I haven't had much success thus far.

-Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200629/a7bd6169/attachment.html>

From dustin at buildbot.net  Tue Jun 30 15:00:02 2020
From: dustin at buildbot.net (dustin at buildbot.net)
Date: Tue, 30 Jun 2020 15:00:02 GMT
Subject: [devel@bb.net] Buildbot Weekly Summary
Message-ID: <202006301500.05UF02GQ033463@trac.buildbot.net>

An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20200630/f7ac424b/attachment.html>