All of lore.kernel.org
 help / color / mirror / Atom feed
From: nobuhiro1.iwamatsu@toshiba.co.jp (nobuhiro1.iwamatsu at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.19.y-cip] Update CI to use the latest	linux-cip-ci containers
Date: Thu, 1 Aug 2019 23:30:10 +0000	[thread overview]
Message-ID: <OSAPR01MB323492C44097529D77D8AAE892DE0@OSAPR01MB3234.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190731220244.20321-2-chris.paterson2@renesas.com>

Hi Chris,

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Chris
> Paterson
> Sent: Thursday, August 1, 2019 7:03 AM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] [PATCH 4.19.y-cip] Update CI to use the latest
> linux-cip-ci containers
> 
> The main aim of this update is to add support for more build architectures.
> 
> In addition, we need to include a fix so that builds using Kernel configs
> from cip-kernel-config will work again, after changes to the directory
> structure caused us problems.
> 
> Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>

Applied, thanks.

Best regards,
  Nobuhiro

> ---
>  .gitlab-ci.yml | 22 ++++++++++++----------
>  1 file changed, 12 insertions(+), 10 deletions(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index
> 96eed0e0c81a..fb775f4950b1 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -2,16 +2,17 @@ variables:
>    GIT_STRATEGY: clone
>    GIT_DEPTH: 10
>    DOCKER_DRIVER: overlay2
> +  DOCKER_IMAGE_TAG: v2
> 
> -build_arm_renesas_shmobile_defconfig:
> +arm_renesas_shmobile_defconfig:
>    stage: build
> -  image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
> +  image:
> +
> registry.gitlab.com/cip-playground/linux-cip-ci:build-$DOCKER_IMAGE_
> TA
> + G
>    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
> +    DTBS: r8a7743-iwg20d-q7-dbcm-ca.dtb
> + r8a7745-iwg22d-sodimm-dbhd-ca.dtb
>    script:
>      - /opt/build_kernel.sh
>    artifacts:
> @@ -20,15 +21,15 @@ build_arm_renesas_shmobile_defconfig:
>      paths:
>        - output
> 
> -build_arm64_renesas_defconfig:
> +arm64_renesas_defconfig:
>    stage: build
> -  image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
> +  image:
> +
> registry.gitlab.com/cip-playground/linux-cip-ci:build-$DOCKER_IMAGE_
> TA
> + G
>    variables:
>      BUILD_ARCH: arm64
>      CONFIG: renesas_defconfig
>      CONFIG_LOC: cip-kernel-config
>      DEVICES: r8a774c0-ek874
> -    DTBS: arch/arm64/boot/dts/renesas/r8a774c0-ek874.dtb
> +    DTBS: r8a774c0-ek874.dtb
>    script:
>      - /opt/build_kernel.sh
>    artifacts:
> @@ -37,15 +38,15 @@ build_arm64_renesas_defconfig:
>      paths:
>        - output
> 
> -build_arm_shmobile_defconfig:
> +arm_shmobile_defconfig:
>    stage: build
> -  image: registry.gitlab.com/cip-playground/linux-cip-ci:build-v1
> +  image:
> +
> registry.gitlab.com/cip-playground/linux-cip-ci:build-$DOCKER_IMAGE_
> TA
> + G
>    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
> +    DTBS: r8a7743-iwg20d-q7-dbcm-ca.dtb
> + r8a7745-iwg22d-sodimm-dbhd-ca.dtb
>    script:
>      - /opt/build_kernel.sh
>    artifacts:
> @@ -56,10 +57,11 @@ build_arm_shmobile_defconfig:
> 
>  run_tests:
>    stage: test
> -  image: registry.gitlab.com/cip-playground/linux-cip-ci:test-v1
> +  image:
> +
> registry.gitlab.com/cip-playground/linux-cip-ci:test-$DOCKER_IMAGE_T
> AG
>    when: always
>    variables:
>      GIT_STRATEGY: none
> +    TEST_TIMEOUT: 30
>    script:
>      - /opt/submit_tests.sh
>    artifacts:
> --
> 2.17.1
> 
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

  reply	other threads:[~2019-08-01 23:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 22:02 [cip-dev] [PATCH 4.19.y-cip-rt] Update CI to use the latest linux-cip-ci containers Chris Paterson
2019-07-31 22:02 ` [cip-dev] [PATCH 4.19.y-cip] " Chris Paterson
2019-08-01 23:30   ` nobuhiro1.iwamatsu at toshiba.co.jp [this message]
2019-07-31 22:02 ` [cip-dev] [PATCH 4.4.y-cip-rt] " Chris Paterson
2019-08-01 23:30   ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-31 22:02 ` [cip-dev] [PATCH 4.4.y-cip] " Chris Paterson
2019-08-01 23:30   ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-08-01 18:32 ` [cip-dev] [PATCH 4.19.y-cip-rt] " Ben Hutchings
2019-08-02  7:22   ` Chris Paterson
2019-08-01 23:30 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-08-02 10:34   ` Jan Kiszka

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=OSAPR01MB323492C44097529D77D8AAE892DE0@OSAPR01MB3234.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --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.