From: chris.paterson2@renesas.com (Chris Paterson)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH v3 4.19.y-cip] Add gitlab-ci.yaml
Date: Mon, 8 Jul 2019 14:15:36 +0100 [thread overview]
Message-ID: <20190708131536.17087-1-chris.paterson2@renesas.com> (raw)
In-Reply-To: <20190702105122.23718-1-chris.paterson2@renesas.com>
This is configured to build and test the following configurations:
* BUILD_ARCH: arm
* CONFIG: renesas_shmobile_defconfig
* CONFIG_LOC: cip-kernel-config
* DEVICES: r8a7743-iwg20d-q7 r8a7745-iwg22d-sodimm
* DTBS: r8a7743-iwg20d-q7-dbcm-ca.dtb r8a7745-iwg22d-sodimm-dbhd-ca.dtb
* BUILD_ARCH: arm64
* CONFIG: renesas_defconfig
* CONFIG_LOC: cip-kernel-config
* DEVICES: r8a774c0-ek874
* DTBS: r8a774c0-ek874.dtb
* BUILD_ARCH: arm
* CONFIG: shmobile_defconfig
* CONFIG_LOC: intree
* DEVICES: r8a7743-iwg20d-q7 r8a7745-iwg22d-sodimm
* DTBS: r8a7743-iwg20d-q7-dbcm-ca.dtb r8a7745-iwg22d-sodimm-dbhd-ca.dtb
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>
---
v2->v3: Updated to use linux-cip-ci version: ad4a6589 (docker tag "v1")
v1->v2: Updated to use latest linux-cip-ci version: 9d56f41a
.gitlab-ci.yml | 68 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 68 insertions(+)
create mode 100644 .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 000000000000..96eed0e0c81a
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +1,68 @@
+variables:
+ GIT_STRATEGY: clone
+ GIT_DEPTH: 10
+ DOCKER_DRIVER: overlay2
+
+build_arm_renesas_shmobile_defconfig:
+ stage: build
+ image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
+ variables:
+ BUILD_ARCH: arm
+ CONFIG: renesas_shmobile_defconfig
+ CONFIG_LOC: cip-kernel-config
+ DEVICES: r8a7743-iwg20d-q7 r8a7745-iwg22d-sodimm
+ DTBS: arch/arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dtb arch/arm/boot/dts/r8a7745-iwg22d-sodimm-dbhd-ca.dtb
+ script:
+ - /opt/build_kernel.sh
+ artifacts:
+ name: "$CI_JOB_NAME"
+ when: on_success
+ paths:
+ - output
+
+build_arm64_renesas_defconfig:
+ stage: build
+ image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
+ variables:
+ BUILD_ARCH: arm64
+ CONFIG: renesas_defconfig
+ CONFIG_LOC: cip-kernel-config
+ DEVICES: r8a774c0-ek874
+ DTBS: arch/arm64/boot/dts/renesas/r8a774c0-ek874.dtb
+ script:
+ - /opt/build_kernel.sh
+ artifacts:
+ name: "$CI_JOB_NAME"
+ when: on_success
+ paths:
+ - output
+
+build_arm_shmobile_defconfig:
+ stage: build
+ image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
+ variables:
+ BUILD_ARCH: arm
+ CONFIG: shmobile_defconfig
+ CONFIG_LOC: intree
+ DEVICES: r8a7743-iwg20d-q7 r8a7745-iwg22d-sodimm
+ DTBS: arch/arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dtb arch/arm/boot/dts/r8a7745-iwg22d-sodimm-dbhd-ca.dtb
+ script:
+ - /opt/build_kernel.sh
+ artifacts:
+ name: "$CI_JOB_NAME"
+ when: on_success
+ paths:
+ - output
+
+run_tests:
+ stage: test
+ image: registry.gitlab.com/cip-playground/linux-cip-ci:test-v1
+ when: always
+ variables:
+ GIT_STRATEGY: none
+ script:
+ - /opt/submit_tests.sh
+ artifacts:
+ name: "$CI_JOB_NAME"
+ paths:
+ - output
--
2.17.1
next prev parent reply other threads:[~2019-07-08 13:15 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
2019-07-08 13:15 ` Chris Paterson [this message]
2019-07-08 13:31 ` [cip-dev] [PATCH v3 " 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=20190708131536.17087-1-chris.paterson2@renesas.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.