Re: [isar-cip-core][PATCH 4/4] enable cip-core-image-kernelci

Jan Kiszka

On 07.01.22 14:40, Alice Ferrazzi wrote:
On Fri, Jan 7, 2022 at 8:18 PM Jan Kiszka <jan.kiszka@...> wrote:

On 07.01.22 11:23, Alice Ferrazzi wrote:
On Fri, Jan 7, 2022 at 7:07 PM Jan Kiszka <jan.kiszka@...> wrote:

On 07.01.22 11:02, Alice Ferrazzi wrote:
On Thu, Jan 6, 2022 at 11:12 PM Jan Kiszka <jan.kiszka@...> wrote:

On 06.01.22 12:16, Alice Ferrazzi wrote:
enable CIP core image KernelCI to be built with gitlab pipeline
and uploaded to the KernelCI storage using KernelCI API.
enable cip-core-image-kernelci to be built for amd64, arm and arm64.

Signed-off-by: Alice Ferrazzi <alice.ferrazzi@...>
.gitlab-ci.yml | 40 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 39 insertions(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index e7db8c1..784343b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -9,6 +9,7 @@ variables:
targz: disable
dtb: none
deploy: enable
+ deploy_kernelci: disable

- build
@@ -37,7 +38,8 @@ default:
- if [ "${release}" = "bullseye" ]; then base_yaml="${base_yaml}:kas/opt/bullseye.yml"; fi;
- echo "Building ${base_yaml}"
- kas build ${base_yaml}
- - if [ "${deploy}" = "enable" ]; then scripts/ ${release} ${target} ${extension} ${dtb} ${CI_COMMIT_REF_SLUG}; fi
+ - if [ "${deploy}" = "enable" ]; then scripts/ ${release} ${target} ${extension} ${dtb} ${CI_COMMIT_REF_SLUG}; fi;
+ - if [ "${deploy_kernelci}" = "enable" ]; then scripts/ ${release} ${target} ${extension} ${dtb}; fi
Does gitlab-ci forces us to add that closing ; to the last-but-one
command? If so, better add it to the new from the beginning.
I'm just following the syntax that is already there.
The gitlab-ci.yml file syntax preceding my commit is also doing same
thing of adding that closing ; to the last-but-one command.
You can check it here
Then, if the closing semicolon is needed, add it to the new line as well
to avoid having to touch that when adding the next one.
sorry I'm not understanding what you want me to do.
The closing semicolon is needed to the last-but-one command.
Adding it to the last command break the script.
Are you really sure about the closing semicolon?
you are right. I just checked my pipeline backlog and found that some
months ago,
I just checked for both without ; and not the case of both having it.
Still we are changing the syntax already present and used.
is it ok to use a new syntax? if is ok I can send a revision.
I've sent a patch that removes the superfluous semicolons, you were on
CC. Just rebase on top and follow that new pattern.


Siemens AG, Technology
Competence Center Embedded Linux

Join { to automatically receive all group messages.