All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris.Paterson2@renesas.com (Chris Paterson)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH v2 4.19.y-cip] Add gitlab-ci.yaml
Date: Thu, 4 Jul 2019 09:23:16 +0000	[thread overview]
Message-ID: <TYAPR01MB2285DF67F19A34BDE3C95697B7FA0@TYAPR01MB2285.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190702105122.23718-1-chris.paterson2@renesas.com>

Hello all,

It was decided in the weekly meeting today by the maintainers that we will add the .gitlab-ci.yml files (i.e. this patch) to the main kernel.org repository.

However, I've been busy this week and already have more changes to make.

So please drop this patch and I'll submit a V3 in the next few days.

I'll mark it accordingly in patchwork.

Kind regards, Chris

> From: Chris Paterson <chris.paterson2@renesas.com>
> Sent: 02 July 2019 11:51
> 
> This is configured to build and test for the following configurations:
> 
> 1.
> ARCH: arm
> CONFIGS: shmobile_defconfig
> BOARDS: r8a7743-iwg20d, r8a7745-iwg22d
> 2.
> ARCH: arm64
> CONFIGS: defconfig
> BOARDS: r8a774c0-ek874
> 
> Over time support will be added for all CIP supported architectures and
> configurations.
> 
> At the moment only simple boot tests are run. Real tests will be added in
> the future.
> 
> Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
> ---
> 
> v1->v2: Updated to use latest linux-cip-ci version: 9d56f41a
> 
> I still prefer to have these .gitlab-ci.yml files in the main cip repo,
> rather then split them off into their own repo and trigger them with
> hooks. Any opinions Kernel maintainers?
> 
> 
>  .gitlab-ci.yml | 35 +++++++++++++++++++++++++++++++++++
>  1 file changed, 35 insertions(+)
>  create mode 100644 .gitlab-ci.yml
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> new file mode 100644
> index 000000000000..71d92c975723
> --- /dev/null
> +++ b/.gitlab-ci.yml
> @@ -0,0 +1,35 @@
> +variables:
> +  GIT_STRATEGY: clone
> +  GIT_DEPTH: "10"
> +  DOCKER_DRIVER: overlay2
> +
> +build_arm_shmobile_defconfig:
> +  stage: build
> +  image: registry.gitlab.com/cip-playground/linux-cip-ci:build-latest
> +  script:
> +    - /opt/build_kernel.sh arm shmobile_defconfig
> +  artifacts:
> +    name: "$CI_JOB_NAME"
> +    when: on_success
> +    paths:
> +      - output
> +
> +build_arm64_defconfig:
> +  stage: build
> +  image: registry.gitlab.com/cip-playground/linux-cip-ci:build-latest
> +  script:
> +    - /opt/build_kernel.sh arm64 defconfig
> +  artifacts:
> +    name: "$CI_JOB_NAME"
> +    when: on_success
> +    paths:
> +      - output
> +
> +run_tests:
> +  stage: test
> +  image: registry.gitlab.com/cip-playground/linux-cip-ci:test-latest
> +  when: always
> +  before_script: []
> +  script:
> +    - /opt/submit_tests.sh
> +
> --
> 2.17.1

  reply	other threads:[~2019-07-04  9:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 13:12 [cip-dev] [PATCH 4.19.y-cip] Add gitlab-ci.yaml Chris Paterson
2019-06-27 13:12 ` [cip-dev] [PATCH 4.4.y-cip] " Chris Paterson
2019-06-28  0:20   ` daniel.sangorrin at toshiba.co.jp
2019-06-28  5:48     ` Jan Kiszka
2019-06-28  7:14       ` Chris Paterson
2019-07-02 10:51   ` [cip-dev] [PATCH v2 " Chris Paterson
2019-07-04  9:23     ` Chris Paterson
2019-07-08 13:16     ` [cip-dev] [PATCH v3 " Chris Paterson
2019-07-08 13:31       ` Chris Paterson
2019-07-11 10:58       ` Pavel Machek
2019-07-02 10:51 ` [cip-dev] [PATCH v2 4.19.y-cip] " Chris Paterson
2019-07-04  9:23   ` Chris Paterson [this message]
2019-07-08 13:15   ` [cip-dev] [PATCH v3 " Chris Paterson
2019-07-08 13:31     ` Chris Paterson
2019-07-11 10:56     ` Pavel Machek
2019-07-11 11:03     ` Pavel Machek

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=TYAPR01MB2285DF67F19A34BDE3C95697B7FA0@TYAPR01MB2285.jpnprd01.prod.outlook.com \
    --to=chris.paterson2@renesas.com \
    --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 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.