diff mbox series

[4/4] .gitlab-ci.yml: use Debian 12-based container image with curl / tar 1.35

Message ID 20250206072321.677851-4-peter@korsgaard.com
State Accepted
Headers show
Series [1/4] support/docker: move to current bookworm (Debian 12) snapshot | expand

Commit Message

Peter Korsgaard Feb. 6, 2025, 7:23 a.m. UTC
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Romain Naour Feb. 6, 2025, 8:36 a.m. UTC | #1
Hello Peter, All,

Le 06/02/2025 à 08:23, Peter Korsgaard a écrit :
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  .gitlab-ci.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 3d7719568f..7eba876a54 100644
> --- a/.gitlab-ci.yml
> +++ 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

Best regards,
Romain


>  
>  stages:
>    - generate-gitlab-ci
Peter Korsgaard Feb. 6, 2025, 9:03 a.m. UTC | #2
>>>>> "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?
Romain Naour Feb. 6, 2025, 9:19 a.m. UTC | #3
Le 06/02/2025 à 10:03, Peter Korsgaard a écrit :
>>>>>> "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?
> 

Last time I used my personal gitlab fork to trigger a new pipeline and local
builds when gitlab-ci minutes was exhausted... but it takes a lot of time.

I guess you needs some volunteers to tests this update.

Is it ok to push a testing branch to trigger a pipeline for the runtime tests?

Best regards,
Romain
Peter Korsgaard Feb. 6, 2025, 2:37 p.m. UTC | #4
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:

Hi,

 >> Sure, how do we trigger a test run before merging to master?

 > Last time I used my personal gitlab fork to trigger a new pipeline and local
 > builds when gitlab-ci minutes was exhausted... but it takes a lot of time.

 > I guess you needs some volunteers to tests this update.

 > Is it ok to push a testing branch to trigger a pipeline for the runtime tests?

Yes please (I see you alredy did) - Thanks!
Peter Korsgaard Feb. 9, 2025, 9:22 p.m. UTC | #5
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
 > Hi,

 >>> Sure, how do we trigger a test run before merging to master?

 >> Last time I used my personal gitlab fork to trigger a new pipeline and local
 >> builds when gitlab-ci minutes was exhausted... but it takes a lot of time.

 >> I guess you needs some volunteers to tests this update.

 >> Is it ok to push a testing branch to trigger a pipeline for the runtime tests?

 > Yes please (I see you alredy did) - Thanks!

With the basic shellcheck and flake8 issues fixed I have now
rebuilt/repushed the container and applied the series, thanks.
diff mbox series

Patch

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 3d7719568f..7eba876a54 100644
--- a/.gitlab-ci.yml
+++ 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
 
 stages:
   - generate-gitlab-ci