All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 2/2] GitLab CI: crude mapping of PMM's scripts to jobs
Date: Mon, 9 Mar 2020 23:53:43 -0400	[thread overview]
Message-ID: <20200310035343.GA50141@localhost.localdomain> (raw)
In-Reply-To: <e7aea58f-8ed0-239f-04d8-934c8c00e51d@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Thu, Feb 06, 2020 at 02:05:04PM +0100, Philippe Mathieu-Daudé wrote:
> > 
> > On another thread Thomas said he doesn't want to be responsible of other
> > tests:
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg670132.html
> > 
> > We could move the set of tests converted from Peter personal testsuite
> > into a separate YAML, so the interested (you Cleber, and Peter) can have
> > a F: entry in MAINTAINERS for it:
> > 
> > include:
> >    - local: '/.gitlab-ci-pm215.yml'

Yep, I agree this is a good idea. I'll be following that pattern.

> 
> I'm not calling this file "pm215" because Peter owns it, but because it
> would contains all the tests Peter was running manually before we use GitLab
> as a gating CI.
> 
> 

One small difference is that I feel that Peter wants this to be
less about him, and more about a established set of jobs to gate on.

So, I'll be using the ".gitlab-ci-gating.yml" file name for now, unless
my perception is badly calibrated. :)

Thanks!
- Cleber.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-10  3:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  3:23 [RFC PATCH 1/2] GitLab CI: avoid calling before_scripts on unintended jobs Cleber Rosa
2020-02-03  3:23 ` [RFC PATCH 2/2] GitLab CI: crude mapping of PMM's scripts to jobs Cleber Rosa
2020-02-03 17:36   ` Wainer dos Santos Moschetta
2020-02-07 19:34     ` Cleber Rosa
2020-02-08 13:02       ` Peter Maydell
2020-03-10  5:01         ` Cleber Rosa
2020-03-10  9:30           ` Peter Maydell
2020-02-06 13:03   ` Philippe Mathieu-Daudé
2020-02-06 13:05     ` Philippe Mathieu-Daudé
2020-03-10  3:53       ` Cleber Rosa [this message]
2020-02-06 13:52     ` Wainer dos Santos Moschetta
2020-02-06 13:54       ` Philippe Mathieu-Daudé
2020-02-06 15:13         ` Thomas Huth
2020-02-07  8:37   ` Thomas Huth
2020-02-07 10:05     ` Thomas Huth
2020-02-07 11:08     ` Alex Bennée
2020-02-07 19:59       ` Cleber Rosa
2020-02-07 16:26     ` Peter Maydell
2020-02-07 19:27       ` Cleber Rosa
2020-02-08 12:51         ` Peter Maydell
2020-02-07 19:46     ` Cleber Rosa
2020-02-03 15:26 ` [RFC PATCH 1/2] GitLab CI: avoid calling before_scripts on unintended jobs Wainer dos Santos Moschetta
2020-02-03 16:08 ` Thomas Huth
2020-02-07 20:01   ` Cleber Rosa

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=20200310035343.GA50141@localhost.localdomain \
    --to=crosa@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.