All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] .gitlab-ci.yml: do runtime tests only on explicit trigger
Date: Sat, 20 Oct 2018 23:54:32 -0300	[thread overview]
Message-ID: <5bcbea684f4e4_3ef22b2051d8a8b4760e3@ultri5.mail> (raw)
In-Reply-To: 20181020224254.5895-1-arnout@mind.be

Hello,

On Sat, Oct 20, 2018 at 07:42 PM, Arnout Vandecappelle (Essensium/Mind) wrote:

[snip]
> +++ b/.gitlab-ci.yml
> @@ -62,6 +62,11 @@ check-package:
>              - output/build/packages-file-list.txt
>  
>  .runtime_test: &runtime_test
> +    # Running the runtime tests for every push is too much, so limit to
> +    # explicit triggers through the API.
> +    only:
> +        - triggers
> +        - tags
>      # Keep build directories so the rootfs can be an artifact of the job. The
>      # runner will clean up those files for us.
>      # Multiply every emulator timeout by 10 to avoid sporadic failures in
> @@ -261,71 +266,3 @@ zynq_zc706_defconfig: *defconfig
>  zynq_zed_defconfig: *defconfig
>  zynq_zybo_defconfig: *defconfig
>  zynqmp_zcu106_defconfig: *defconfig
> -tests.boot.test_atf.TestATFAllwinner: *runtime_test
> -tests.boot.test_atf.TestATFMarvell: *runtime_test
> -tests.boot.test_atf.TestATFVexpress: *runtime_test
[snip]

You forgot to re-run 'make .gitlab-ci.yml'.
We don't want to remove the test list.

> +++ b/.gitlab-ci.yml.in
> @@ -62,6 +62,11 @@ check-package:
>              - output/build/packages-file-list.txt
>  
>  .runtime_test: &runtime_test
> +    # Running the runtime tests for every push is too much, so limit to
> +    # explicit triggers through the API.
> +    only:
> +        - triggers
> +        - tags

We could also allow a regexp on the branch name to trigger it:
         - /^.*-runtime_test$/

Using the same commit, I pushed 2 branches:
branch name: gitlabci-triggers, #jobs = 4
https://gitlab.com/RicardoMartincoski/buildroot/pipelines/33723520
branch name: gitlabci-triggers-runtime_test, #jobs = 72
https://gitlab.com/RicardoMartincoski/buildroot/pipelines/33723541

>      # Keep build directories so the rootfs can be an artifact of the job. The
>      # runner will clean up those files for us.
>      # Multiply every emulator timeout by 10 to avoid sporadic failures in
> -- 

Regards,
Ricardo

  reply	other threads:[~2018-10-21  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 22:42 [Buildroot] [PATCH] .gitlab-ci.yml: do runtime tests only on explicit trigger Arnout Vandecappelle
2018-10-21  2:54 ` Ricardo Martincoski [this message]
2018-10-21 11:23   ` Arnout Vandecappelle
2018-10-22  2:35     ` Ricardo Martincoski
2018-10-22 23:08       ` Arnout Vandecappelle
2018-10-23  3:13         ` Ricardo Martincoski

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=5bcbea684f4e4_3ef22b2051d8a8b4760e3@ultri5.mail \
    --to=ricardo.martincoski@gmail.com \
    --cc=buildroot@busybox.net \
    /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.