RFC: Gitlab CI for barebox
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.
Signature · 7 lines
Best regards, Antony Pavlov _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hello Antony,
Quoted 3 lines · Antony Pavlov
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at:
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.
Quoted 4 lines
Sample
gitlab-ci.yamlconfig 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
Quoted 8 lines
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.
Quoted 1 line
* 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.
Quoted 2 lines
* 'build doc' produces sphinx generated html docs archive artifact
* 'build ARM/MIPS/RISC-V/X86/sandbox' produce log/ directory archive artifacts
Nice.
Quoted 1 line
* 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?
Quoted 4 lines
@Ahmad
I suppose we can add your qemu
barebox/test/emulate.pltests 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
Signature · 9 lines
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 [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Quoted 36 lines · Ahmad Fatoum
Hello Antony,
Quoted 3 lines · Antony Pavlov
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at: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.
Quoted 4 lines
Sample
gitlab-ci.yamlconfig 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
Quoted 5 lines
Corresponding gitlab pipeline results:
Quoted 6 lines
Quoted 3 lines
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.
Yes, I disable these checks for my build tests. Getting these issues resolved only holds for a certain time. Overall bloat will break it sooner or later anyway :(
It's fighting against windmills.
Quoted 6 lines
Quoted 2 lines
* 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.
I'm not sure we even have all binaries. I guess some of the mvebu startup binaries would have to be extracted from the hardware and I don't know if we are allowed to share them for download if we extracted them.
Sascha
Signature · 9 lines
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 [email protected] http://lists.infradead.org/mailman/listinfo/barebox
On Mon, 31 Jan 2022 11:39:45 +0100
Ahmad Fatoum <[email protected]> wrote:
Hello Ahmad!
Quoted 20 lines · Antony Pavlov
Quoted 3 lines
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at: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.
Quoted 1 line
Quoted 7 lines
Quoted 3 lines
Sample
gitlab-ci.yamlconfig 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
I have just update gitlab runner, please see https://gitlab.com/frantony/barebox-gitlab-ci-runner/-/commit/f90c3932f1e90f900c4d4304c6a54898a5ee0e1e
As a result runner can build barebox for openrisc architecture and run emulate.pl, see
https://gitlab.com/frantony/barebox/-/pipelines/464224894
There is a problem with emulate.pl for MIPS (see https://gitlab.com/frantony/barebox/-/jobs/2058215656).
log/mips/console_main artifact contains the fragment:
---- begin ----
Hit any to stop autoboot: 3
barebox@qemu malta:/ echo "YGIS""XTJCSB"
YGISXTJCSB
barebox@qemu malta:/ echo -o /cmd 'cat /env/data/config'; echo "EOVL""SAWCFS"; sh /cmd; echo "EOVL""SAWCFS" $?; EOVLSAWCFS
could not open /env/data/config: No such file or directory
EOVLSAWCFS 1
barebox@qemu malta:/ echo -o /cmd selftest; echo "BOCZ""OJHGFV"; sh /cmd; echo "BOCZ""OJHGFV" $?; BOCZOJHGFV
printf: all 116 tests passedprogress_notifier: all 12 tests passed
BOCZOJHGFV 0
barebox@qemu malta:/
---- end ----
there is a problem: "could not open /env/data/config: No such file or directory"
How we can pass error to gitlab runner? Now runner reports that there is no error.
Quoted 9 lines
Quoted 4 lines
@Ahmad
I suppose we can add your qemu
barebox/test/emulate.pltests into CI.Here is the Github action config for the tests:
https://github.com/a3f/barebox/blob/emulate.pl/.github/workflows/vm-tests.yamlAny thoughts on how/if to integrate with the mailing list?
I suppose gitlab itself can send e-mails on CI pipeline fail.
Signature · 7 lines
Best regards, Antony Pavlov _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Quoted 58 lines · On Sat, 5 Feb 2022 17:12:33 +0300 Antony Pavlov <[email protected]> wrote:
On Mon, 31 Jan 2022 11:39:45 +0100
Ahmad Fatoum <[email protected]> wrote:Hello Ahmad!
Quoted 20 lines · Antony Pavlov
Quoted 3 lines
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at: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.
Quoted 1 line
Quoted 7 lines
Quoted 3 lines
Sample
gitlab-ci.yamlconfig 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
I have just update gitlab runner, please see https://gitlab.com/frantony/barebox-gitlab-ci-runner/-/commit/f90c3932f1e90f900c4d4304c6a54898a5ee0e1e
As a result runner can build barebox for openrisc architecture and run emulate.pl, see
https://gitlab.com/frantony/barebox/-/pipelines/464224894There is a problem with emulate.pl for MIPS (see https://gitlab.com/frantony/barebox/-/jobs/2058215656).
log/mips/console_main artifact contains the fragment:
---- begin ----
Hit any to stop autoboot: 3
barebox@qemu malta:/ echo "YGIS""XTJCSB"
YGISXTJCSB
barebox@qemu malta:/ echo -o /cmd 'cat /env/data/config'; echo "EOVL""SAWCFS"; sh /cmd; echo "EOVL""SAWCFS" $?; EOVLSAWCFS
could not open /env/data/config: No such file or directory
EOVLSAWCFS 1
barebox@qemu malta:/ echo -o /cmd selftest; echo "BOCZ""OJHGFV"; sh /cmd; echo "BOCZ""OJHGFV" $?; BOCZOJHGFV
printf: all 116 tests passedprogress_notifier: all 12 tests passed
BOCZOJHGFV 0
barebox@qemu malta:/
---- end ----
Quoted 1 line
there is a problem: "could not open /env/data/config: No such file or directory"
The same problem with ARM architecture.
It looks like CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW_IKCONFIG=y is set only in RISC-V virt{32/64}_defconfig.
Signature · 7 lines
Best regards, Antony Pavlov _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hello Antony,
Quoted 61 lines · Antony Pavlov
Quoted 58 lines · On Sat, 5 Feb 2022 17:12:33 +0300 Antony Pavlov <[email protected]> wrote:
On Mon, 31 Jan 2022 11:39:45 +0100
Ahmad Fatoum <[email protected]> wrote:Hello Ahmad!
Quoted 20 lines · Antony Pavlov
Quoted 3 lines
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at: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.
Quoted 1 line
Quoted 7 lines
Quoted 3 lines
Sample
gitlab-ci.yamlconfig 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
I have just update gitlab runner, please see https://gitlab.com/frantony/barebox-gitlab-ci-runner/-/commit/f90c3932f1e90f900c4d4304c6a54898a5ee0e1e
As a result runner can build barebox for openrisc architecture and run emulate.pl, see
https://gitlab.com/frantony/barebox/-/pipelines/464224894There is a problem with emulate.pl for MIPS (see https://gitlab.com/frantony/barebox/-/jobs/2058215656).
log/mips/console_main artifact contains the fragment:
---- begin ----
Hit any to stop autoboot: 3
barebox@qemu malta:/ echo "YGIS""XTJCSB"
YGISXTJCSB
barebox@qemu malta:/ echo -o /cmd 'cat /env/data/config'; echo "EOVL""SAWCFS"; sh /cmd; echo "EOVL""SAWCFS" $?; EOVLSAWCFS
could not open /env/data/config: No such file or directory
EOVLSAWCFS 1
barebox@qemu malta:/ echo -o /cmd selftest; echo "BOCZ""OJHGFV"; sh /cmd; echo "BOCZ""OJHGFV" $?; BOCZOJHGFV
printf: all 116 tests passedprogress_notifier: all 12 tests passed
BOCZOJHGFV 0
barebox@qemu malta:/
---- end ----
Quoted 4 lines
Quoted 1 line
there is a problem: "could not open /env/data/config: No such file or directory"
The same problem with ARM architecture.
It looks likeCONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW_IKCONFIG=yis set only in RISC-V virt{32/64}_defconfig.
There is a fallback to get .config out of the build directory instead.
Alternatively, you can call emulate.pl with --kconfig-add CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW_IKCONFIG=y
Cheers,
Ahmad
Quoted 1 line
Signature · 9 lines
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 [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Quoted 58 lines · Antony Pavlov
On Mon, 31 Jan 2022 11:39:45 +0100
Ahmad Fatoum <[email protected]> wrote:Hello Ahmad!
Quoted 20 lines · Antony Pavlov
Quoted 3 lines
Hi!
I have made simple Gitlab CI for barebox.
Nice.
Quoted 4 lines
Gitlab CI runner setup instruction and
the source for Debian 11 docker image can be found at: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.
Quoted 1 line
Quoted 7 lines
Quoted 3 lines
Sample
gitlab-ci.yamlconfig 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
I have just update gitlab runner, please see https://gitlab.com/frantony/barebox-gitlab-ci-runner/-/commit/f90c3932f1e90f900c4d4304c6a54898a5ee0e1e
As a result runner can build barebox for openrisc architecture and run emulate.pl, see
https://gitlab.com/frantony/barebox/-/pipelines/464224894There is a problem with emulate.pl for MIPS (see https://gitlab.com/frantony/barebox/-/jobs/2058215656).
log/mips/console_main artifact contains the fragment:
---- begin ----
Hit any to stop autoboot: 3
barebox@qemu malta:/ echo "YGIS""XTJCSB"
YGISXTJCSB
barebox@qemu malta:/ echo -o /cmd 'cat /env/data/config'; echo "EOVL""SAWCFS"; sh /cmd; echo "EOVL""SAWCFS" $?; EOVLSAWCFS
could not open /env/data/config: No such file or directory
EOVLSAWCFS 1
barebox@qemu malta:/ echo -o /cmd selftest; echo "BOCZ""OJHGFV"; sh /cmd; echo "BOCZ""OJHGFV" $?; BOCZOJHGFV
printf: all 116 tests passedprogress_notifier: all 12 tests passed
BOCZOJHGFV 0
barebox@qemu malta:/
---- end ----
Quoted 3 lines
there is a problem: "could not open /env/data/config: No such file or directory"
How we can pass error to gitlab runner? Now runner reports that there is no error.
That's ok. It's preferable to have the config built into barebox, but the fallback for getting the .config out of the build directory seems to work alright.
Quoted 14 lines
Quoted 10 lines
Quoted 5 lines
@Ahmad
I suppose we can add your qemu
barebox/test/emulate.pltests into CI.Here is the Github action config for the tests:
https://github.com/a3f/barebox/blob/emulate.pl/.github/workflows/vm-tests.yamlAny thoughts on how/if to integrate with the mailing list?
I suppose gitlab itself can send e-mails on CI pipeline fail.
Signature · 9 lines
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 [email protected] http://lists.infradead.org/mailman/listinfo/barebox