From: chris.paterson2@renesas.com (Chris Paterson)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip] Add gitlab-ci.yaml
Date: Thu, 27 Jun 2019 14:12:50 +0100 [thread overview]
Message-ID: <20190627131250.7932-2-chris.paterson2@renesas.com> (raw)
In-Reply-To: <20190627131250.7932-1-chris.paterson2@renesas.com>
This is configured to build and test for the following configuration:
1. ARCH: arm
CONFIGS: shmobile_defconfig
BOARDS: r8a7743-iwg20d
Build/test Docker containers and scripts are created by the
https://gitlab.com/cip-playground/linux-cip-ci repository.
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. These changes should all all be handled in
the linux-cip-ci repository.
Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
---
In theory this file is only required in our GitLab repository. However if
we add it there the automatic mirroring from the kernel.org repository
will be broken.
I also tried the GitLab option to create a new repository for CI/CD
'only'. However this also has the exact same problem.
This means that the best/easiest approach will be to just add the
.gitlab-ci.yml file directly to the kernel.org repository. Most people can
ignore it.
There may well be some chrun in this file as linux-cip-ci improves, but
this is a good starting point.
.gitlab-ci.yml | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 .gitlab-ci.yml
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
new file mode 100644
index 000000000000..4e949ac75b7b
--- /dev/null
+++ b/.gitlab-ci.yml
@@ -0,0 +1,27 @@
+variables:
+ GIT_STRATEGY: none
+ DOCKER_DRIVER: overlay2
+
+before_script:
+ - cd /opt/linux
+ - git fetch origin
+ - git checkout $CI_COMMIT_SHA
+
+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
+
+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
next prev parent reply other threads:[~2019-06-27 13:12 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 ` Chris Paterson [this message]
2019-06-28 0:20 ` [cip-dev] [PATCH 4.4.y-cip] " 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 ` [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=20190627131250.7932-2-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.