From 9446589056f620acad2e29cff3c774249ae4524c Mon Sep 17 00:00:00 2001
From: gitbot <gitbot@garz-fricke.com>
Date: Wed, 6 Jul 2022 12:50:37 +0000
Subject: [PATCH] Integrate
gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more
--
Commit: https://git.seco.com/seco-ne/yocto/infrastructure/gitlab-ci/-/commit/c503a6d442e77bd1761d815ffcda7e19a9f71048
CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build
The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been
defined outside the job in the '.gitlab-ci.yml' file. This has a lower
precedence then variables defined inside the job, but it seems that
these variables are used in the scope of 'Trigger variables' when
available in the trigger job. These override the value set in the
template. As main results this made FNGSystem jobs build the normal
yocto.
---
.gitlab-ci | 2 +-
.gitlab-ci.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci b/.gitlab-ci
index ea3aa81..c503a6d 160000
--- a/.gitlab-ci
+++ b/.gitlab-ci
@@ -1 +1 @@
-Subproject commit ea3aa8164756750f9e8fbfd642ea1ebdf871fc5a
+Subproject commit c503a6d442e77bd1761d815ffcda7e19a9f71048
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 69b0793..82a84f3 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -4,7 +4,7 @@
# ---------------------------------------------------------------------------------------
include:
- project: '${CI_PROJECT_ROOT_NAMESPACE}/yocto/infrastructure/gitlab-ci'
- ref: ea3aa8164756750f9e8fbfd642ea1ebdf871fc5a
+ ref: c503a6d442e77bd1761d815ffcda7e19a9f71048
file: 'manifest-integration-yocto.yml'
variables:
--
GitLab