public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Luis Machado via Gdb <gdb@sourceware.org>
Subject: Re: [RFC] Proposal for hosting GDB CI builds
Date: Thu, 01 Jul 2021 11:40:32 +0200	[thread overview]
Message-ID: <yddczs21ien.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <7bfae273-3887-30c8-dc65-94d5b177db56@linaro.org> (Luis Machado via Gdb's message of "Wed, 30 Jun 2021 13:46:07 -0300")

Hi Luis,

> Linaro can take care of providing builders and build jobs for ARM. Other
> architectures would be handled by their respective contributors. Those 
> contributors can write jobs and plug builders as needed.

thanks for coming forward with this: this is very welcome, given how
easy it is to miss build failures and other issues especially on
not-so-common targets.

However, is there any documentation on setting up new builders?  I've
never dealt with Jenkins before, and from glimpsing over the docs some
time ago when Jeff Law talked about extending this GCC builders to a
wider range of architectures left me completely at a loss: the whole
thing felt like a total moloch with an incredible range of abilities,
but little to no guidance on how to start.  If the GDB CI wants to
extend beyond a Linux-only range of targets, I believe considerable
documentation is necessary to make this happen.

Besides, I seem to have glimpsed from the Linaro instance that the
builders use Docker.  Is this a requirement or just a convenience?  I'm
asking because there's no current Docker port to Solaris (there used to
be one based on zones, but it's no longer maintained) and the
buildbot-based builders I'm running (for both LLVM and GDB) do fine
without.

Thanks.
        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2021-07-01  9:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 16:46 Luis Machado
2021-07-01  9:40 ` Rainer Orth [this message]
2021-07-01 11:48   ` Luis Machado
2021-07-01 12:06     ` Rainer Orth
2021-07-01 13:10       ` Luis Machado
2021-07-02  9:05         ` Rainer Orth
2021-07-01 11:37 ` Christophe LYON
2021-07-01 11:50   ` Luis Machado
2021-07-01 12:08     ` Rainer Orth
2021-07-20 15:21 ` Luis Machado
2021-07-23 20:17   ` Simon Marchi

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=yddczs21ien.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb@sourceware.org \
    /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).