From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] .gitlab-ci.yml: use Debian 12-based container image with curl / tar 1.35
Date: Thu, 06 Feb 2025 10:03:15 +0100 [thread overview]
Message-ID: <87o6zfigx8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <e7c06d15-5581-4a26-abfa-5a826e181108@smile.fr> (Romain Naour's message of "Thu, 6 Feb 2025 09:36:01 +0100")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
Hi,
>> +++ b/.gitlab-ci.yml
>> @@ -1,7 +1,7 @@
>> # Configuration for Gitlab-CI.
>> # Builds appear on https://gitlab.com/buildroot.org/buildroot/pipelines
>>
>> -image: $CI_REGISTRY/buildroot.org/buildroot/base:20230207.1123
>> +image: $CI_REGISTRY/buildroot.org/buildroot/base:20250205.1514
> This requires some testing with the Buildroot testsuite. Some tests may requires
> an update due to qemu version change.
> See this commit as example:
> https://gitlab.com/buildroot.org/buildroot/-/commit/d8447c38f53f98e1df4a209e9f70e54f8b60f36e
Sure, how do we trigger a test run before merging to master?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-06 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 7:23 [Buildroot] [PATCH 1/4] support/docker: move to current bookworm (Debian 12) snapshot Peter Korsgaard
2025-02-06 7:23 ` [Buildroot] [PATCH 2/4] support/docker: add curl Peter Korsgaard
2025-02-06 7:23 ` [Buildroot] [PATCH 3/4] support/docker: add tar 1.35 Peter Korsgaard
2025-02-06 7:23 ` [Buildroot] [PATCH 4/4] .gitlab-ci.yml: use Debian 12-based container image with curl / " Peter Korsgaard
2025-02-06 8:36 ` Romain Naour via buildroot
2025-02-06 9:03 ` Peter Korsgaard [this message]
2025-02-06 9:19 ` Romain Naour via buildroot
2025-02-06 14:37 ` Peter Korsgaard
2025-02-09 21:22 ` Peter Korsgaard
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=87o6zfigx8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.