Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] support/scripts: prioritize conditions for pipeline creation
Date: Tue, 22 Sep 2020 21:30:51 +0200	[thread overview]
Message-ID: <20200922213051.3668d826@windsurf> (raw)
In-Reply-To: <080dfb07851ab4a84287dede9e03c99b217e73fc.1600722514.git.yann.morin.1998@free.fr>

On Mon, 21 Sep 2020 23:08:41 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> When multiple conditions match simultaneously, even though that should
> not happen in practice, we want the more "important" one to win over
> the less "important" ones. For example, a tag is more important than a
> branch name or a trigger.
> 
> Currently, the latest condition to match takes precendence over any
> previous one, while we want the exact opposite.
> 
> Fix that with proper fallbacks in else-blocks.
> 
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
>  support/scripts/generate-gitlab-ci-yml | 58 +++++++++++++-------------
>  1 file changed, 29 insertions(+), 29 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-09-22 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 21:08 [Buildroot] [PATCH 0/2] gitlab-ci: fix and handle the weekly scheduled pipeline (branch yem/gitlab-ci-schedule) Yann E. MORIN
2020-09-21 21:08 ` [Buildroot] [PATCH 1/2] support/scripts: prioritize conditions for pipeline creation Yann E. MORIN
2020-09-22 19:30   ` Thomas Petazzoni [this message]
2020-09-21 21:08 ` [Buildroot] [PATCH 2/2] support/scripts: handle scheduled pipelines Yann E. MORIN

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=20200922213051.3668d826@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox