public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Serhei Makarov <serhei@serhei.io>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] Add full roster of fedora/rhel/centos-stream stap workers and builders
Date: Tue, 23 Apr 2024 23:19:25 +0200	[thread overview]
Message-ID: <20240423211925.GE28568@gnu.wildebeest.org> (raw)
In-Reply-To: <a18cec35-3269-4f98-85ee-bf64edcfa29a@app.fastmail.com>

Hi Serhei,

On Tue, Apr 23, 2024 at 04:56:58PM -0400, Serhei Makarov wrote:
> The full set of buildbots will take a bit more time to bring up,
> but I'm sending them in one patch now for simplicity's sake.
> ---
>  buildbot.config.sample |   7 +++
>  builder/master.cfg     | 130 ++++++++++++++++++++++++++++++++++++++++-
>  2 files changed, 134 insertions(+), 3 deletions(-)
> 
> diff --git a/buildbot.config.sample b/buildbot.config.sample
> index 10ff37c..1f6304d 100644
> --- a/buildbot.config.sample
> +++ b/buildbot.config.sample
> @@ -33,6 +33,13 @@ starfive-2=frob
>  starfive-3=frob
>  starfive-4=frob
>  stap-fedrawhide-x86_64=frob
> +stap-fedora41-x86_64=frob
> +stap-fedora40-x86_64=frob
> +stap-fedora39-x86_64=frob

So 41 is current rawhide, 40 is the latest stable fedora release and
39 is old stable. Would it make sense to name "rawhide",
"fedora-latest" and "fedora-old-stable" or something like that? Then
you don't have to rename them every few months.

The x86_64 containers are called debian-stable, debian-testing,
fedora-rawhide and fedora-latest.

Cheers,

Mark

  parent reply	other threads:[~2024-04-23 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 20:56 Serhei Makarov
2024-04-23 21:12 ` Frank Ch. Eigler
2024-04-23 21:16   ` Serhei Makarov
2024-04-23 21:19 ` Mark Wielaard [this message]
2024-04-23 21:24   ` Frank Ch. Eigler
2024-04-23 21:37     ` Serhei Makarov
2024-04-23 21:44     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240423211925.GE28568@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=serhei@serhei.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).