Integrate gitlab-ci/separate-images-in-multiple-pipelines and 1 more

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9406ad75

Yocto build: separate images in multiple pipelines

Instead of building the Yocto image, the Yocto SDK and the FNGSystem
image in one single pipeline, separate them into three independent
pipelines that are triggered in parallel.

This makes the concept more modular: we have a single general pipeline
now which is configurable from outside via variables. Hence we can have
a custom number of pipelines along with custom build targets in each
project without having to make code changes in the gitlab-ci project.

The default Yocto manifest pipeline configures three build pipelines:

- yocto-build-jobs
- sdk-build-jobs
- fngsystem-build-jobs

In a project including the Yocto manifest pipeline, we can disable
certain build pipelines using job rules, e.g. disabling the SDK build:

sdk-build-jobs:
  rules:
    - when: never

Furthermore we can add more pipelines by simply adding jobs extending
the '.build-jobs' class in the project's .gitlab-ci.yml:

yocto-custom-build-jobs:
  extends:
    - .build-jobs
  variables:
    BITBAKE_TASK: build
    CI_PARAM_IMAGE: custom-image
    CI_PARAM_DISTRO: custom-distro
    PACKAGE_TYPE: image

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@447804d2

.gitlab-ci: increase analyze timeout

.gitlab-ci @ 9406ad75

-Subproject commit 5762a54c150e5848b2262dba53df1a335af42ae9
+Subproject commit 9406ad752cfe28ca33556df57282c278ef9ece00

.gitlab-ci.yml

@@ -4,11 +4,11 @@
 # ---------------------------------------------------------------------------------------
 include:
   - project: '${CI_PROJECT_ROOT_NAMESPACE}/yocto/infrastructure/gitlab-ci'
-    ref: 5762a54c150e5848b2262dba53df1a335af42ae9
+    ref: 9406ad752cfe28ca33556df57282c278ef9ece00
     file: 'manifest-integration.yml'
 
 variables:
-  GITLAB_CI_REVISION: 5762a54c150e5848b2262dba53df1a335af42ae9
+  GITLAB_CI_REVISION: 9406ad752cfe28ca33556df57282c278ef9ece00
   BB_RECIPE_NAME: linux-imx
   # FIXME: This is only necessary due to the following GitLab limitation:
   # https://gitlab.com/gitlab-org/gitlab/-/issues/209904