Integrate meta-seconorth-machine/update-gitlab-ci

Commit: seco-ne/yocto/layers/meta-seconorth-machine@3c880db4

Integrate gitlab-ci/share-build-and-test-job-basics

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@075aeccb

Refactoring: share build and test job basics for ci-test and Yocto

This shares YAML code for the following procedures:

• Build environment
• Source code checkout via repo
• SSH key and known hosts setup
• LAVA test submission
• Docker check if build folder is empty

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@180fb023

Integrate gitlab-ci/CI-hardcoded-artifact-path-for-fngsystem

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800

CI: Add hardcoded artifact's path generation also for fng system

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@9e57f620

Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c503a6d4

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.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@e8fed12b

Integrate gitlab-ci/CI-readd-allow-failure-true

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ea3aa816

CI: Readd allow_failure:true to fix not finished pipelines

According to the docs a manual job always has allow_failure set to true, but we see a lot of jobs staying in an unfinished state since the removal of the allow_failure: true keyword for the sdk and test jobs. This should fix the broken behaviour.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@ce63d1ef

Integrate gitlab-ci/test-artifact-upload

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc0503b6

CI: Hardcode the artifacts path in the generated job description

Some gitlab update(?) seem to have changed the behaviour in variable passing. In the scripts the variables are available but in the artifacts path does not resolve them any more. May be it has something to do with the introduction of the trigger:forward keyword.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@f854a078

Integrate gitlab-ci/really-include-yamllint-in-manifest-pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@f39e65ab

Manifest: really include yamllint in the full pipeline

Previous commit did not have the effect due to wrong extend order.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@7be7421e

Integrate gitlab-ci/sdk-deployment and 5 more

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0dd147c8

SDK: Remove package step from build sdk, add sdk to artifacts, create deploy_sdk

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ecab2962

Manifest: include yamllint in full pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4071423

Manifest pipeline: run full build pipeline when triggered via web UI

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8862b213

Manifest refactoring: move job rules into classes

This way they can be reused instead of redefining them in each job.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@d604b330

Fix wrong remote name in ci-test pipeline

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@e810c2ac

Fix wrong manifest project ID for ci-test pipeline

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@cfa6b992

Integrate gitlab-ci/share-manifest-pipeline and 2 more

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9b8cf51c

Share manifest pipeline for ci-test and yocto

Combine all common yaml parts in manifest-pipeline.yml and add manifest-pipeline-yocto.yml and manifest-pipeline-ci-test.yml containing the different variable assignments for each environment.

This change implicitly introduces parent-child build job generation in the ci-test pipeline, like it is done in the yocto pipeline already. The ci-test build jobs have been moved to build-jobs-ci-test.jinja2 accordingly.

Furthermore rename GITLAB_CI_CURRENT_REV to GITLAB_CI_REVISION and remove the run conditions from all generated build jobs, since these are already present in the upstream trigger job.

The repos including these files have to be updated with the new file and variable names.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1b939fe

Use CI variables in build template directly

The job generation script implicitly passes the OS environment to the template, so that the template has access to all GitLab CI variables. Hence there is no need to explicitly pass any of them as command line arguments.

This change makes the "generate-build-jobs" job more generic, so that it can be shared with the ci-test pipeline in the future.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@775c09c1

Add gitlab_backup script to download all project exports of a gitlab group

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@f3add766

Integrate gitlab-ci/fix-build-merge-request-job and 1 more

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@7f68f307

Yocto manifest build: re-enable build:merge_request job

This job was accidentally disabled in 2e6c1b4, because it was included in the generated child pipeline. This pipeline is not created on the master, though, so the condition for the job was never met.

Move the job to the parent pipeline again, so that it gets executed on the master like before.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@970c7fd7

Re-add yamllint stage to ci test manifest pipeline

Was accidentally removed in previous commit.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@1427c222

Integrate gitlab-ci/define-yamllint-explicitly

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b2bc220

Define yamllint job explicitly in each pipeline

The yamllint job was included in the pipeline implicitly via the inclusion of common.yml. This is not very transparent. Make the common definition a base job and extend it explicitly in each pipeline now.

Add infrastructure stage comment header into both yaml files.