qemu-arm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH-for-6.0 v4 16/17] gitlab-ci: Make some ARM 32-bit jobs option


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH-for-6.0 v4 16/17] gitlab-ci: Make some ARM 32-bit jobs optional
Date: Sun, 8 Nov 2020 23:00:31 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1

On 11/8/20 9:45 PM, Philippe Mathieu-Daudé wrote:
> The armel/armhf targets have a lot in common. Instead of
> testing both user/system emulation on each target, test
> each one once. Mark the other combination optional, so
> user can still run the tests manually.
> 
> We now test system-mode emulation on armel target, and
> user-mode emulation to armhf target:
> 
> - armel-system          Yes
> - armel-user            Optional
> - armhf-system          Optional
> - armhf-user            Yes
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> Cc: qemu-arm@nongnu.org
> Cc: Laurent Vivier <laurent@vivier.eu>
> ---
>  .gitlab-ci.d/crossbuilds.yml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
> index 03ebfabb3fa..e4526e98232 100644
> --- a/.gitlab-ci.d/crossbuilds.yml
> +++ b/.gitlab-ci.d/crossbuilds.yml
> @@ -32,11 +32,17 @@ cross-armel-user:
>    <<: *cross_user_build_job_definition
>    variables:
>      IMAGE: debian-armel-cross
> +  rules:

As I only want to restrict this to push events, I'll add:

       - if: '$CI_PIPELINE_SOURCE != "push"'
         when: always

So all other events (merge request, pipeline triggered via WebUI)
the job is automatically executed.

> +    - when: manual
> +      allow_failure: true
>  
>  cross-armhf-system:
>    <<: *cross_system_build_job_definition
>    variables:
>      IMAGE: debian-armhf-cross
> +  rules:
> +    - when: manual
> +      allow_failure: true

Ditto (and in the MIPS job in next patch).

>  
>  cross-armhf-user:
>    <<: *cross_user_build_job_definition
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]