public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Luis Machado via Gdb <gdb@sourceware.org>
Subject: Re: [RFC] Proposal for hosting GDB CI builds
Date: Thu, 1 Jul 2021 08:48:28 -0300	[thread overview]
Message-ID: <0e30f5d9-9f2f-05bd-1d02-30424017c6d7@linaro.org> (raw)
In-Reply-To: <yddczs21ien.fsf@CeBiTec.Uni-Bielefeld.DE>

Hi Rainer,

On 7/1/21 6:40 AM, Rainer Orth wrote:
> 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.

I know the feeling. I've been there myself as Jenkins is indeed a very 
flexible tool. And I don't, by any means, claim to be an expert on 
dealing with it.

Usually what I do is to peak at the documentation and at what others 
have implemented. Then I work on extending/modifying things to my needs.

The GDB build job (currently running for aarch64/armhf/x86_64) I put 
together is here:

https://git.linaro.org/ci/job/configs.git/tree/tcwg-gdb.yaml

But I expect we will have to adjust this to make it a bit more generic 
so other architectures can use it.

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

That is a convenience so we can share hardware resources. It is possible 
to use real hardware to run the jobs. One may need to adjust the 
configurations a bit (distro, packages etc), but a job can automate some 
of that. Details about distros to use and packages to install still need 
to be investigated/discussed.

> 
> Thanks.
>          Rainer
> 

  reply	other threads:[~2021-07-01 11:48 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
2021-07-01 11:48   ` Luis Machado [this message]
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=0e30f5d9-9f2f-05bd-1d02-30424017c6d7@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=gdb@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).