cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH linux-4.4.y-cip] gitlab-ci: Use external linux-cip-pipelines repository to define CI
Date: Fri, 22 Nov 2019 11:51:20 +0100	[thread overview]
Message-ID: <20191122105120.GE30479@amd> (raw)
In-Reply-To: <20191121160008.4886-3-chris.paterson2@renesas.com>

Hi!

> Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
>  .gitlab-ci.yml | 283 +------------------------------------------------
>  1 file changed, 3 insertions(+), 280 deletions(-)

Thanks, I applied this, too, and I already see the green ticks.

I won't touch the -rt branches for now, they'll get the updates when
merging from -cip.

Best regards,
								Pavel

> +include:
> +  - https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/raw/master/linux-cip-pipeline.yml
> +  - https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/raw/master/trees/linux-4.4.y-cip.yml

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191122/1be64a04/attachment.sig>

  reply	other threads:[~2019-11-22 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 16:00 [cip-dev] [PATCH linux-4.19.y-cip] gitlab-ci: Use external linux-cip-pipelines repository to define CI Chris Paterson
2019-11-21 16:00 ` [cip-dev] [PATCH linux-4.19.y-cip-rt] " Chris Paterson
2019-11-21 16:00 ` [cip-dev] [PATCH linux-4.4.y-cip] " Chris Paterson
2019-11-22 10:51   ` Pavel Machek [this message]
2019-11-21 16:00 ` [cip-dev] [PATCH linux-4.4.y-cip-rt] " Chris Paterson
2019-11-22  9:18 ` [cip-dev] [PATCH linux-4.19.y-cip] " Pavel Machek
2020-01-31 13:02 ` Jan Kiszka
2020-02-03  8:51   ` Chris Paterson

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=20191122105120.GE30479@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    /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;
as well as URLs for NNTP newsgroup(s).