From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <sha@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: RFC: Gitlab CI for barebox
Date: Sun, 30 Jan 2022 15:00:11 +0300 [thread overview]
Message-ID: <20220130150011.e8b22a088b654f6a0b0f96de@gmail.com> (raw)
Hi!
I have made simple Gitlab CI for barebox.
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
Sample gitlab-ci.yaml config file:
https://gitlab.com/frantony/barebox/-/commit/b1ed597d8e67c8f76f4f98cd1c6605b936cf2471
Corresponding gitlab pipeline results:
https://gitlab.com/frantony/barebox/-/pipelines/459422690
Some notes:
* there are several "images size > maximum size" errors during 'build ARM'
* fake firmware blobs for ARM are used
* 'build doc' produces sphinx generated html docs archive artifact
* 'build ARM/MIPS/RISC-V/X86/sandbox' produce log/ directory archive artifacts
* no support for kvx, openrisc and powerpc
@Ahmad
I suppose we can add your qemu barebox/test/emulate.pl tests into CI.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2022-01-30 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 12:00 Antony Pavlov [this message]
2022-01-31 10:39 ` Ahmad Fatoum
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=20220130150011.e8b22a088b654f6a0b0f96de@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--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