mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>,
	Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org, Jules Maselbas <jmaselbas@kalray.eu>
Subject: Re: RFC: Gitlab CI for barebox
Date: Mon, 31 Jan 2022 11:39:45 +0100	[thread overview]
Message-ID: <9b440929-d7e8-da69-a4b0-dcca1f5a5ce7@pengutronix.de> (raw)
In-Reply-To: <20220130150011.e8b22a088b654f6a0b0f96de@gmail.com>

Hello Antony,

On 30.01.22 13:00, Antony Pavlov wrote:
> Hi!
> 
> I have made simple Gitlab CI for barebox.

Nice.

> Gitlab CI runner setup instruction and
> the source for Debian 11 docker image can be found at:
> 
>   https://gitlab.com/frantony/barebox-gitlab-ci-runner

I had tried something similar, but with Github actions

https://github.com/a3f/barebox/actions/runs/740206381

I didn't have the time to pursue this further. I am fine
with Gitlab as well.

> 
> Sample gitlab-ci.yaml config file:
> 
>   https://gitlab.com/frantony/barebox/-/commit/b1ed597d8e67c8f76f4f98cd1c6605b936cf2471

Here's how it looks for Github actions with emulate.pl:

https://github.com/a3f/barebox/blob/emulate.pl/.github/workflows/build-configs.yaml


> Corresponding gitlab pipeline results:
> 
>   https://gitlab.com/frantony/barebox/-/pipelines/459422690
> 
> 
> Some notes:
> 
>   * there are several "images size > maximum size" errors during 'build ARM'

Ye. IIRC Sascha disables these for his build tests..? Would be nice to get
those resolved sometime.

>   * fake firmware blobs for ARM are used

Could we just fetch them from the correct location? That way we could
just provide the prebuilt binaries for download. But for a first step,
fakes are fine.

>   * 'build doc' produces sphinx generated html docs archive artifact
>   * 'build ARM/MIPS/RISC-V/X86/sandbox' produce log/ directory archive artifacts

Nice.

>   * no support for kvx, openrisc and powerpc

My GA script supports openrisc. Perhaps Jules is interested in getting
CI working for kvx as well once we have the infrastructure in place?

> 
> @Ahmad
> 
> I suppose we can add your qemu barebox/test/emulate.pl tests into CI.

Here is the Github action config for the tests:
https://github.com/a3f/barebox/blob/emulate.pl/.github/workflows/vm-tests.yaml

Any thoughts on how/if to integrate with the mailing list?

Cheers,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2022-01-31 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 12:00 Antony Pavlov
2022-01-31 10:39 ` Ahmad Fatoum [this message]
2022-01-31 11:12   ` Sascha Hauer
2022-02-05 14:12   ` Antony Pavlov
2022-02-08 16:16     ` Antony Pavlov
2022-02-08 18:30       ` Ahmad Fatoum
2022-02-08 18:33     ` Ahmad Fatoum

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=9b440929-d7e8-da69-a4b0-dcca1f5a5ce7@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jmaselbas@kalray.eu \
    --cc=sha@pengutronix.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