public inbox for
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <>
To: Sam James <>
Subject: Re: Builder credentials request for Gentoo/sparc
Date: Fri, 13 Jan 2023 15:41:44 -0500	[thread overview]
Message-ID: <Y8HCCMlMcO4t/> (raw)
In-Reply-To: <>

Hi -

> As discussed on #overseers, I'd like to start off with some easy
> builds with a Buildbot on our beefy sparc machine in Gentoo.


> For now, let's say normal core count should be 8, and bursts of 16,
> but we can crank that up significantly later. We'll start with just
> bzip2.  It's okay to do 3-4 builds at a time. Again, we can probably
> crank that up later.

bzip2 will produce approximately zero traffic, never mind 3-4 at a
time.  Check out for the
projects that are producing lots of buildbot traffic, and maybe choose
one or more of those.

> Is there a way for me to trigger builds on demand at first, so I can
> test if everything is working?

If you have commit access to any repo from which builds are sent to
your worker, that's one way.  I'm not sure of more directed ways.

> I believe I need a password for my end. Thanks!

Sent under separate cover.

- FChE

  reply	other threads:[~2023-01-13 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 20:17 Sam James
2023-01-13 20:41 ` Frank Ch. Eigler [this message]
2023-01-13 20:46   ` Sam James
2023-01-15 15:46   ` 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:

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

  git send-email \
    --in-reply-to=Y8HCCMlMcO4t/ \ \ \ \

* 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).