From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/kexec: bump to version 2.0.29
Date: Sun, 4 Aug 2024 21:43:21 +0200 [thread overview]
Message-ID: <20240804214321.30c1d66a@windsurf> (raw)
In-Reply-To: <644363c1b32b75633da922333b075c8e@free.fr>
Hello Julien,
On Sun, 04 Aug 2024 19:34:50 +0200
Julien Olivain <ju.o@free.fr> wrote:
> Yes, I was aware of this functionality (from the manual). I quickly
> tried it a while back, and was not able to make it work. At that time,
> I thought this CI was limited to paid users, or gitlab users having
> their own runners (which I don't have), or Buildroot maintainers
> (i.e. project members).
>
> Reading your explanation here, and reading again the Buildroot
> documentation at:
> https://nightly.buildroot.org/manual.html#_runtime_tests_and_gitlab_ci
> I now understand I should be able start CI jobs on my own.
>
> I tested again (a bit harder this time) with this Kexec runtime test
> as you described. After resolving few (GitLab) issues I was finally
> able to make it work. For example:
> https://gitlab.com/jolivain/buildroot/-/jobs/7455292795
Nice!
> I will propose some Buildroot documentation updates. I hope this
> will help more users to use this nice feature. Specifically:
>
> - write explicitly this CI works with a "Free" gitlab user account.
>
> - add a note to make sure "GitLab Instance Runners" are enabled
> in the forked project. In my case, they were disabled.
>
> - add a note about setting the job timeout. In my case, it was
> set to "1h", which was too short in many cases. Right now, I've
> set 4h for simple tests.
>
> - document all the other recognized branch name formats by the script:
> https://gitlab.com/buildroot.org/buildroot/-/blob/2024.05.1/support/scripts/generate-gitlab-ci-yml?ref_type=tags#L60
Such updates to the documentation would definitely be welcome for sure!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-04 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 17:37 [Buildroot] [PATCH 1/1] package/kexec: bump to version 2.0.29 Julien Olivain
2024-07-21 16:17 ` Thomas Petazzoni via buildroot
2024-07-22 13:13 ` Thomas Petazzoni via buildroot
2024-07-28 13:09 ` Julien Olivain
2024-07-28 14:19 ` Thomas Petazzoni via buildroot
2024-08-04 17:34 ` Julien Olivain
2024-08-04 19:43 ` Thomas Petazzoni via buildroot [this message]
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=20240804214321.30c1d66a@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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