Skip to contentSkip to conversation

Add gitlab-ci.yaml

PATCH New Chris Paterson 4 participants 16 messages Jun 27, 2019 – Jul 11, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Add gitlab-ci.yaml

This is configured to build and test for the following configurations:

1. ARCH: arm
CONFIGS: shmobile_defconfig
BOARDS: r8a7743-iwg20d

2. ARCH: arm64
CONFIGS: defconfig
BOARDS: r8a774c0-ek874

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.

---

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 | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 .gitlab-ci.yml
.gitlab-ci.yml new file +39 -0
new file mode 100644
index 000000000000..d619ef0c1969
@@ -0,0 +1,39 @@
+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
+
+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
+
Signature · 1 line
2.17.1
#1 lore raw

PATCH 1/1 Add gitlab-ci.yaml

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.

---

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
.gitlab-ci.yml new file +27 -0
new file mode 100644
index 000000000000..4e949ac75b7b
@@ -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
Signature · 1 line
2.17.1
#2 lore raw

PATCH 1/1 Add gitlab-ci.yaml

It seems that a lot of people have the same problem.
https://gitlab.com/gitlab-org/gitlab-ce/issues/15041

Quoted 81 lines

-----Original Message-----
From: cip-dev-bounces at lists.cip-project.org <[email protected]> On Behalf Of Chris Paterson
Sent: Thursday, June 27, 2019 10:13 PM
To: cip-dev at lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip] Add gitlab-ci.yaml

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.

---

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
.gitlab-ci.yml new file +27 -1
new file mode 100644
index 000000000000..4e949ac75b7b
@@ -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

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

#3 lore raw

PATCH 1/1 Add gitlab-ci.yaml

Quoted 2 lines · daniel.sangorrin at toshiba.co.jp

It seems that a lot of people have the same problem.
https://gitlab.com/gitlab-org/gitlab-ce/issues/15041

Maybe a combination of a CI-only repo and a hook that triggers a build on changes in the external (and unchanged) source repo can do the trick.

Jan

Quoted 87 lines
Quoted 78 lines

-----Original Message-----
From: cip-dev-bounces at lists.cip-project.org <[email protected]> On Behalf Of Chris Paterson
Sent: Thursday, June 27, 2019 10:13 PM
To: cip-dev at lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip] Add gitlab-ci.yaml

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.

---

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

.gitlab-ci.yml new file +27 -1
new file mode 100644
index 000000000000..4e949ac75b7b
@@ -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

Quoted 4 lines

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

Signature · 2 lines
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
#4 lore raw

PATCH 1/1 Add gitlab-ci.yaml

Quoted 10 lines

From: Jan Kiszka <[email protected]>
Sent: 28 June 2019 06:48

Quoted 2 lines · daniel.sangorrin at toshiba.co.jp

It seems that a lot of people have the same problem.
https://gitlab.com/gitlab-org/gitlab-ce/issues/15041

Maybe a combination of a CI-only repo and a hook that triggers a build on changes in the external (and unchanged) source repo can do the trick.

Yes this is one solution, however you wouldn't get the pretty green ticks that show a commit has been verified.

Chris

Quoted 95 lines

Jan

Quoted 3 lines
Quoted 3 lines

-----Original Message-----
From: cip-dev-bounces at lists.cip-project.org <[email protected]

project.org> On Behalf Of Chris Paterson

Quoted 75 lines
Quoted 75 lines

Sent: Thursday, June 27, 2019 10:13 PM
To: cip-dev at lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip] Add gitlab-ci.yaml

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.

---

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

.gitlab-ci.yml new file +27 -1
new file mode 100644
index 000000000000..4e949ac75b7b
@@ -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

Quoted 9 lines
Quoted 4 lines

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

#5 lore raw

PATCH v2 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

This is configured to build and test for the following configurations:

1.
ARCH: arm
CONFIGS: shmobile_defconfig
BOARDS: r8a7743-iwg20d, r8a7745-iwg22d

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.

---

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 | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 .gitlab-ci.yml
.gitlab-ci.yml new file +23 -0
new file mode 100644
index 000000000000..aec787a353bc
@@ -0,0 +1,23 @@
+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
+
+run_tests:
+  stage: test
+  image: registry.gitlab.com/cip-playground/linux-cip-ci:test-latest
+  when: always
+  before_script: []
+  script:
+    - /opt/submit_tests.sh
Signature · 1 line
2.17.1
#6 lore raw

PATCH v2 1/1 Add gitlab-ci.yaml

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

Quoted 60 lines

From: Chris Paterson <[email protected]>
Sent: 02 July 2019 11:52

This is configured to build and test for the following configurations:

1.
ARCH: arm
CONFIGS: shmobile_defconfig
BOARDS: r8a7743-iwg20d, r8a7745-iwg22d

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.

---

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 | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 .gitlab-ci.yml
.gitlab-ci.yml new file +23 -1
new file mode 100644
index 000000000000..aec787a353bc
@@ -0,0 +1,23 @@
+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
+
+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

#7 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

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: 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

---

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 | 51 ++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 .gitlab-ci.yml
.gitlab-ci.yml new file +51 -0
new file mode 100644
index 000000000000..421d971908a6
@@ -0,0 +1,51 @@
+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_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
Signature · 1 line
2.17.1
#8 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

Hello all,

Quoted 22 lines

From: Chris Paterson <[email protected]>
Sent: 08 July 2019 14:16

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: 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.

Quoted 7 lines

At the moment only simple boot tests are run. Real tests will be added in the future

---

v2->v3: Updated to use linux-cip-ci version: ad4a6589 (docker tag "v1")

I meant to provide some examples of the below patch in use, but obviously forgot.

This .gitlab-ci.yml file is based on taf 'v1' of Docker images built by linux-cip-ci [1].

Specifically, the below patch has been tested in linux-cip in the chris/linux-4.4.y-cip-ci-test branch [1] as can be seen in the below GitLab CI pipeline:
https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/69891645

Physical board boot tests that were run can be found here:
https://lava.ciplatform.org/scheduler/job/1768
https://lava.ciplatform.org/scheduler/job/1769
https://lava.ciplatform.org/scheduler/job/1770
https://lava.ciplatform.org/scheduler/job/1771

[1] https://gitlab.com/cip-playground/linux-cip-ci
[2] https://gitlab.com/cip-project/cip-kernel/linux-cip/commit/0a231b59ce50c72175f09c776a79ebe6da8eff53

Let me know if you have any questions.

Kind regards, Chris

Quoted 69 lines

v1->v2: Updated to use latest linux-cip-ci version: 9d56f41a

 .gitlab-ci.yml | 51
++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 .gitlab-ci.yml
.gitlab-ci.yml new file +14 -0
new file mode 100644
index 000000000000..421d971908a6
@@ -0,0 +1,51 @@
+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

.gitlab-ci.yml new file +17 -0
+  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

.gitlab-ci.yml new file +20 -1
+  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

Applied
#9 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson
Quoted 14 lines · Chris Paterson

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: 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

Quoted 5 lines

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

Thanks, applied to 4.4-cip, and pushed out.
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- 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/20190711/a9151797/attachment.sig>
#10 lore raw

PATCH v2 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

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.

---

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
.gitlab-ci.yml new file +35 -0
new file mode 100644
index 000000000000..71d92c975723
@@ -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
+
Signature · 1 line
2.17.1
#11 lore raw

PATCH v2 1/1 Add gitlab-ci.yaml

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

Quoted 77 lines

From: Chris Paterson <[email protected]>
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.

---

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
.gitlab-ci.yml new file +35 -1
new file mode 100644
index 000000000000..71d92c975723
@@ -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

#12 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

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

---

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
.gitlab-ci.yml new file +68 -0
new file mode 100644
index 000000000000..96eed0e0c81a
@@ -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
Signature · 1 line
2.17.1
#13 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

Hello all,

Quoted 28 lines

From: Chris Paterson <[email protected]>
Sent: 08 July 2019 14:16

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.

Quoted 7 lines

At the moment only simple boot tests are run. Real tests will be added in the future

---

v2->v3: Updated to use linux-cip-ci version: ad4a6589 (docker tag "v1")

I meant to provide some examples of the below patch in use, but obviously forgot.

This .gitlab-ci.yml file is based on taf 'v1' of Docker images built by linux-cip-ci [1].

Specifically, the below patch has been tested in linux-cip in the chris/linux-4.19.y-cip-ci-test branch [1] as can be seen in the below GitLab CI pipeline:
https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/69891649

Physical board boot tests that were run can be found here:
https://lava.ciplatform.org/scheduler/job/1772
https://lava.ciplatform.org/scheduler/job/1773
https://lava.ciplatform.org/scheduler/job/1774
https://lava.ciplatform.org/scheduler/job/1775
https://lava.ciplatform.org/scheduler/job/1776

[1] https://gitlab.com/cip-playground/linux-cip-ci
[2] https://gitlab.com/cip-project/cip-kernel/linux-cip/commit/192b3a7258c905fb4bdca8e0243923a719acafef

Let me know if you have any questions.

Kind regards, Chris

Quoted 86 lines

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
.gitlab-ci.yml new file +14 -0
new file mode 100644
index 000000000000..96eed0e0c81a
@@ -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

.gitlab-ci.yml new file +34 -0
+  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

.gitlab-ci.yml new file +20 -1
+  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

Applied
#14 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

Hi!

Quoted 14 lines

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

Quoted 8 lines

* 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.

Thanks, applied and pushed out. Sorry for the delay.

Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- 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/20190711/1994ee54/attachment.sig>
#15 lore raw

PATCH v3 1/1 Add gitlab-ci.yaml

In reply to Chris Paterson

Hi!

Quoted 20 lines

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

Quoted 5 lines

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

I went ahead, and applied this to linux-4.19.y-cip-rt-rebase branch, too. If it is easy to add that one to testing, it would be nice.

Best regards,
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- 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/20190711/7a10c05c/attachment.sig>