Select Git revision
Search by author
- Any Author
- authors
-
Alexander Sterger alexander.sterger
-
Andrii Sosiuk
andrii.sosiuk
-
**** group_556_bot_74cce396359e27efa6278607a72ef350
-
Bernd Mierzowski bernd.mierzowski
-
Christian Stimming
christian.stimming
-
Christoph Kutzera christoph.kutzera
-
Christos Karampeazis
-
CI Variables Management Service Account service_account_ci_vars_management
-
Davide Cardillo
davide.cardillo
-
Dietmar Muscholik dietmar.muscholik
-
Dmitry Petrov dmitry.petrov
-
Felix Gerking felix.gerking
-
GitBot
gitbot
-
Git Bot Service Account
service_account_gitbot
-
Hai Nam Tran hai.nam.tran
-
Hilmar Bode hilmar.bode
-
Jan-Ove Korneffel jan-ove.korneffel
-
Jonas Höppner jonas.hoeppner
-
Lorenzo Pagliai
lorenzo.pagliai
-
Lukas Rosky lukas.rosky
- Jul 13, 2022
-
-
GitBot authored-- 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.
-
- Jul 12, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@546c2e50 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-nogplv3@22280218 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-nogplv3@e13c13f6 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-nogplv3@db904b0d 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-nogplv3@12305175 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-nogplv3@4735f8e8 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-nogplv3@9b09b336 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-nogplv3@eef5e74b 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-nogplv3@1a101b88 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-nogplv3@0a8c7287 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.
-
GitBot authored
-- Commit: config@1cc9dc24 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: config@231e7779 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: config@09802c91 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: config@b291be02 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: config@64e3daf5 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: config@8b327116 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: config@a8afe589 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: config@a75ce824 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: config@143834e3 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: config@1348b682 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.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@8311c0f1 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-distro@8046ca4c 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-distro@fdc5d26c 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-distro@5b86ebf2 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-distro@97fba070 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-distro@5714ff50 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-distro@01508ffe 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-distro@ffed82d0 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-distro@28c5fe8e 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-distro@6a04cf81 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.
-
- Jun 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@1f71143f Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6 Remove yaml redundancies in manifest-integration Leave all common yaml parts in manifest-integration.yml and add manifest-integration-yocto.yml and manifest-integration-ci-test.yml containing the different variable assignments for each environment. The repos including these files have to be updated with the new names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096 Harmonize manifest-integration yaml files for yocto and ci-test This is the first step for reducing code duplicates. BCS 746-000807 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9 retrigger: Allow to specify the manifest's remote identifier in a variable Costum manifest may override this variable -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@6d040847 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80 build-jobs.jinja2: Specify master branch variable again If the MASTER_BRANCH_MANIFEST variable is set in the manifest's .gitlab-ci.yml file, it may not find its way to the generated job, if it is not explicitly set during generation. That is done with this patch. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@ac0b8e04 Integrate gitlab-ci/use-parent-child-build-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f Build jobs: Use parent-child jobs to generate needed build jobs * Move all build, deploy and test stubs to the manifest-build.yml * Create a new job to generate and trigger the build jobs dynamically * Add the base jinja2 file for the build jobs. * Add initial docs for the manifest pipeline * Remove unused files -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@ea9a9bc5 Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@4f158f41 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6 Remove yaml redundancies in manifest-integration Leave all common yaml parts in manifest-integration.yml and add manifest-integration-yocto.yml and manifest-integration-ci-test.yml containing the different variable assignments for each environment. The repos including these files have to be updated with the new names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096 Harmonize manifest-integration yaml files for yocto and ci-test This is the first step for reducing code duplicates. BCS 746-000807 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9 retrigger: Allow to specify the manifest's remote identifier in a variable Costum manifest may override this variable -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@0219cbc7 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80 build-jobs.jinja2: Specify master branch variable again If the MASTER_BRANCH_MANIFEST variable is set in the manifest's .gitlab-ci.yml file, it may not find its way to the generated job, if it is not explicitly set during generation. That is done with this patch. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@0af24422 Integrate gitlab-ci/use-parent-child-build-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f Build jobs: Use parent-child jobs to generate needed build jobs * Move all build, deploy and test stubs to the manifest-build.yml * Create a new job to generate and trigger the build jobs dynamically * Add the base jinja2 file for the build jobs. * Add initial docs for the manifest pipeline * Remove unused files -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@ea28c1fe Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@6593e178 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 2 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6 Remove yaml redundancies in manifest-integration Leave all common yaml parts in manifest-integration.yml and add manifest-integration-yocto.yml and manifest-integration-ci-test.yml containing the different variable assignments for each environment. The repos including these files have to be updated with the new names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096 Harmonize manifest-integration yaml files for yocto and ci-test This is the first step for reducing code duplicates. BCS 746-000807 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9 retrigger: Allow to specify the manifest's remote identifier in a variable Costum manifest may override this variable -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@5ed67733 Integrate gitlab-ci/set-master-branch-manifest-in-jinja2 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80 build-jobs.jinja2: Specify master branch variable again If the MASTER_BRANCH_MANIFEST variable is set in the manifest's .gitlab-ci.yml file, it may not find its way to the generated job, if it is not explicitly set during generation. That is done with this patch. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@24abc379 Integrate gitlab-ci/use-parent-child-build-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f Build jobs: Use parent-child jobs to generate needed build jobs * Move all build, deploy and test stubs to the manifest-build.yml * Create a new job to generate and trigger the build jobs dynamically * Add the base jinja2 file for the build jobs. * Add initial docs for the manifest pipeline * Remove unused files -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@85183ffd Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
GitBot authored
-- Commit: config@b40f13f9 gitlab-ci: set branch variables to kirkstone -- Commit: config@e3625d06 Integrate gitlab-ci/share-yaml-code-for-manifest-integration and 3 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@686323c6 Remove yaml redundancies in manifest-integration Leave all common yaml parts in manifest-integration.yml and add manifest-integration-yocto.yml and manifest-integration-ci-test.yml containing the different variable assignments for each environment. The repos including these files have to be updated with the new names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c751096 Harmonize manifest-integration yaml files for yocto and ci-test This is the first step for reducing code duplicates. BCS 746-000807 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c877f9c9 retrigger: Allow to specify the manifest's remote identifier in a variable Costum manifest may override this variable -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d9660a80 build-jobs.jinja2: Specify master branch variable again If the MASTER_BRANCH_MANIFEST variable is set in the manifest's .gitlab-ci.yml file, it may not find its way to the generated job, if it is not explicitly set during generation. That is done with this patch. -- Commit: config@ee635b23 Integrate gitlab-ci/use-parent-child-build-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2e6c1b4f Build jobs: Use parent-child jobs to generate needed build jobs * Move all build, deploy and test stubs to the manifest-build.yml * Create a new job to generate and trigger the build jobs dynamically * Add the base jinja2 file for the build jobs. * Add initial docs for the manifest pipeline * Remove unused files -- Commit: config@a06c5a58 Integrate gitlab-ci/move-python-scripts-to-subfolder -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1bc683d5 Move python scripts to subfolder BCS 746-000808
-
- Jun 02, 2022
-
-
Tobias Kahlki authoredThe DualEspresso manifest was moved to a custom project. We remove it therefore from the main manifest.
-
- Jun 01, 2022
-
-
GitBot authored
-- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/bc4bd90cc229524bc2d9dcc2eed061845f37faca Integrate gitlab-ci/update-dual-espresso-path and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102 -- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/a06802d3dd89c07ac8446c96ee028c2ae9b770c8 Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/6b1d6b2e1106b0e984af2f2b9b0d1b8f0202b3dd Integrate gitlab-ci/skip-check-via-label and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label -- Commit: https://git.seco.com/seco-ne/yocto/custom/dual-espresso/meta-seconorth-dual-espresso/-/commit/6c8e4274aab48a03f450ac7d3eafb6a21035aee1 Integrate gitlab-ci/allow-check-job-to-fail and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ad9d367e Allow check job to fail This makes merging a project MR possible even if the manifest has received new commits since the MR pipeline build has run. The developer is responsible for deciding whether it is safe to merge it without having a build based on the latest manifest. BCS 746-000794 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@81c2ad85 merge_into_manifest: fix error message if MR already exists
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@1c6ef2d6 Integrate gitlab-ci/update-dual-espresso-path and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102 -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@8f596afd Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@4ffb20b0 Integrate gitlab-ci/skip-check-via-label and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@67f7c664 Integrate gitlab-ci/update-dual-espresso-path and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102 -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@1f9478df Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@b26456f2 Integrate gitlab-ci/skip-check-via-label and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@4bba7d38 Integrate gitlab-ci/update-dual-espresso-path and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102 -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@173d6c1b Integrate gitlab-ci/document-skip-build-label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@8d4e8fd6 Integrate gitlab-ci/skip-check-via-label and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6980d48 Update meta-seconorth-dual-espresso path -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@83002e07 accept_merge_request: explicitly check if MR has merge conflicts According to the documentation [1] we should get a 406 error from the API if we try to merge a merge request which has a merge conflict. We are experiencing a different behaviour, though, where we are getting a 405 error in this case. There is an open GitLab issue on this topic [2]. In our error handling we assumed that the reason for a 405 error is most likely a required pipeline which is still running. This assumtion, however, leads to wrong behaviour in cases where no pipeline is started at all. Fixing this now by explicitly checking for merge conflicts at the very beginning of the error handling sequence. [1]: https://docs.gitlab.com/ee/api/merge_requests.html#merge-a-merge-request [2]: https://gitlab.com/gitlab-org/gitlab/-/issues/364102
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0885629d Document "skip build" label
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e514076 Add possibility to skip MR pipeline check via label -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ee151673 Add possibility to skip MR pipeline build via label
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ad9d367e Allow check job to fail This makes merging a project MR possible even if the manifest has received new commits since the MR pipeline build has run. The developer is responsible for deciding whether it is safe to merge it without having a build based on the latest manifest. BCS 746-000794 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@81c2ad85 merge_into_manifest: fix error message if MR already exists
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338 CI: Add fake lava test to ci-test, reduce fetch depth in update submodule -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c CI: Add variable containing the port for ssh access of the gitlab instance Our server installation uses port 4444 for ssh access. The lava tests didn't took this into account.
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de Rename layers to seconorth
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a CI: Increase infrastructure timeout to 10min
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6 CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c changelog_generator: Use logging instead of print, fix black -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233 CI: Move changelog_generator to gitlab-ci project The script can also be run in the normal python container, so this slightly reduces the complexity. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca Added qt-multi-screen-compositor to project list -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e buildfng: Moved the image and distro variables to global The image and distro for the buildfng job can now be set via global/external variables. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360 Improve CI documentation BCS 746-000636
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b CI: Add check if integration branch is on top of target branch before reusing it The integration branch was reused even if there where new commits on the target branch, which could lead into reverting some changes. This adds a check, if the existing integration branch is directly based on the target branch and deletes it if not. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0 CI: Pull new changelog_generator image, add token to the call. BCS 746-000785 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0 Update README.md: Add description on the gitlab-ci CI and how to deploy
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2b7ec90 CI: Remove build for dual espresso again The pipeline is not setup to build from different manifest and so on, and the dual_espresso manifest will probably go to a seperate repo to keep it private. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@b81d573a CI: Remove '--verbose' from deploy step -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1ebf70c manifest: Added manifest file selection to ci-test -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7 manifest: Added manifest file name to integration script BCS 746-000518 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc6d7858 build: Added DualEspresso -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0941262a layers: Added nogplv3 and dual-espresso layer to CI/CD
-
Tim Jaacks authored -
Tim Jaacks authored
-
Tim Jaacks authored
-
- May 31, 2022
-
-
-- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/b9f73ac8e987d5791d2cf295b492b5884e955e37 Integrate gitlab-ci/fix-port-for-lava-tests and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338 CI: Add fake lava test to ci-test, reduce fetch depth in update submodule -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c CI: Add variable containing the port for ssh access of the gitlab instance Our server installation uses port 4444 for ssh access. The lava tests didn't took this into account. -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/242a65422d764f0136985fa872bfe5193686c8f1 Integrate gitlab-ci/rename-to-seconorth -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de Rename layers to seconorth -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/4b8aff03eecf73c6944cc4771258cf948f577bbf Integrate gitlab-ci/increase-timeout-for-infrastructure-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a CI: Increase infrastructure timeout to 10min -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/83e425eef66586772f83d92189503cea0a7d57fb Integrate gitlab-ci/fix-gitlab-ci-integration -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6 CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/b7bccdc9f51ee44916648f0e46b3286df3d4c353 Integrate gitlab-ci/fix-gitlab-ci-integration and 6 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c changelog_generator: Use logging instead of print, fix black -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233 CI: Move changelog_generator to gitlab-ci project The script can also be run in the normal python container, so this slightly reduces the complexity. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca Added qt-multi-screen-compositor to project list -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e buildfng: Moved the image and distro variables to global The image and distro for the buildfng job can now be set via global/external variables. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360 Improve CI documentation BCS 746-000636 -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/ef096c87c73d8e0161b2b840fe143e90d698b2d2 Integrate gitlab-ci/fix-reuse-of-outdated-integration-branch -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b CI: Add check if integration branch is on top of target branch before reusing it The integration branch was reused even if there where new commits on the target branch, which could lead into reverting some changes. This adds a check, if the existing integration branch is directly based on the target branch and deletes it if not. -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/5e53e95403454060b9596fd7c7dd212d9f73284a Integrate gitlab-ci/changelog-generator and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0 CI: Pull new changelog_generator image, add token to the call. BCS 746-000785 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0 Update README.md: Add description on the gitlab-ci CI and how to deploy -- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-seconorth-dual-espresso/-/commit/9ad657535ed11607f0848f7830c2f54f45c0094a Integrate gitlab-ci/remove-dual-espresso-image-build and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2b7ec90 CI: Remove build for dual espresso again The pipeline is not setup to build from different manifest and so on, and the dual_espresso manifest will probably go to a seperate repo to keep it private. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@b81d573a CI: Remove '--verbose' from deploy step
-
Tobias Kahlki authored
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@56b2019f git: Changed protocol for tools to HTTPS The SRC_URI of the various tools are still using SSH. With the opening of our repositories, SSH isn't available for checkout anymore. Because of this, we changed the protocol to HTTPS instead.
-
Tim Jaacks authored
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@0aac6bde Integrate gitlab-ci/fix-port-for-lava-tests and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338 CI: Add fake lava test to ci-test, reduce fetch depth in update submodule -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c CI: Add variable containing the port for ssh access of the gitlab instance Our server installation uses port 4444 for ssh access. The lava tests didn't took this into account. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@bf43b2e1 Integrate gitlab-ci/rename-to-seconorth -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de Rename layers to seconorth -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@398c13f4 Integrate gitlab-ci/increase-timeout-for-infrastructure-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a CI: Increase infrastructure timeout to 10min -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@12983a3a Integrate gitlab-ci/fix-gitlab-ci-integration -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6 CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@f6bf11c9 Integrate gitlab-ci/fix-gitlab-ci-integration and 6 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c changelog_generator: Use logging instead of print, fix black -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233 CI: Move changelog_generator to gitlab-ci project The script can also be run in the normal python container, so this slightly reduces the complexity. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca Added qt-multi-screen-compositor to project list -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e buildfng: Moved the image and distro variables to global The image and distro for the buildfng job can now be set via global/external variables. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360 Improve CI documentation BCS 746-000636 -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@f9889798 Integrate gitlab-ci/fix-reuse-of-outdated-integration-branch -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b CI: Add check if integration branch is on top of target branch before reusing it The integration branch was reused even if there where new commits on the target branch, which could lead into reverting some changes. This adds a check, if the existing integration branch is directly based on the target branch and deletes it if not. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@3ef0f8ad Integrate gitlab-ci/changelog-generator and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0 CI: Pull new changelog_generator image, add token to the call. BCS 746-000785 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0 Update README.md: Add description on the gitlab-ci CI and how to deploy -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@668b5c03 Integrate gitlab-ci/remove-dual-espresso-image-build and 4 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2b7ec90 CI: Remove build for dual espresso again The pipeline is not setup to build from different manifest and so on, and the dual_espresso manifest will probably go to a seperate repo to keep it private. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@b81d573a CI: Remove '--verbose' from deploy step -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1ebf70c manifest: Added manifest file selection to ci-test -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7 manifest: Added manifest file name to integration script BCS 746-000518 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc6d7858 build: Added DualEspresso
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@fd9b25e0 git: Changed protocol to HTTPS The tools recipes still use SSH as protocol for the checkout. Since we have opend our repository to the public, SSH isn't available anymore. Because of this, we switch to HTTPS as protocol.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@bca16357 Integrate gitlab-ci/fix-port-for-lava-tests and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338 CI: Add fake lava test to ci-test, reduce fetch depth in update submodule -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c CI: Add variable containing the port for ssh access of the gitlab instance Our server installation uses port 4444 for ssh access. The lava tests didn't took this into account. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@88c53f51 Integrate gitlab-ci/rename-to-seconorth -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de Rename layers to seconorth -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@fc026a5d Integrate gitlab-ci/increase-timeout-for-infrastructure-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a CI: Increase infrastructure timeout to 10min -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@be6d5577 Integrate gitlab-ci/fix-gitlab-ci-integration -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6 CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@36e89030 Integrate gitlab-ci/fix-gitlab-ci-integration and 6 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c changelog_generator: Use logging instead of print, fix black -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233 CI: Move changelog_generator to gitlab-ci project The script can also be run in the normal python container, so this slightly reduces the complexity. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca Added qt-multi-screen-compositor to project list -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e buildfng: Moved the image and distro variables to global The image and distro for the buildfng job can now be set via global/external variables. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360 Improve CI documentation BCS 746-000636 -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@9ee19c99 Integrate gitlab-ci/fix-reuse-of-outdated-integration-branch and 2 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b CI: Add check if integration branch is on top of target branch before reusing it The integration branch was reused even if there where new commits on the target branch, which could lead into reverting some changes. This adds a check, if the existing integration branch is directly based on the target branch and deletes it if not. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0 CI: Pull new changelog_generator image, add token to the call. BCS 746-000785 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0 Update README.md: Add description on the gitlab-ci CI and how to deploy -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@554095d5 Integrate gitlab-ci/remove-dual-espresso-image-build and 19 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2b7ec90 CI: Remove build for dual espresso again The pipeline is not setup to build from different manifest and so on, and the dual_espresso manifest will probably go to a seperate repo to keep it private. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@b81d573a CI: Remove '--verbose' from deploy step -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1ebf70c manifest: Added manifest file selection to ci-test -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7 manifest: Added manifest file name to integration script BCS 746-000518 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc6d7858 build: Added DualEspresso -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0941262a layers: Added nogplv3 and dual-espresso layer to CI/CD -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c3a8ff7 CI:package_release: Remove "GUF-" prefix from gitlab artifacts dir BCS 746-000637 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d809d630 manifest-CI: Refactor manifest pipeline files * Split up build and package steps in separate files * Add additional comments * Add log output BCS 746-000637 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c917791b Fix remote name on retrigger stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1ba52853 Move repositories to git.seco.com Rename variable JENKINSGUF_SSH_PRIVATE_KEY / SSH_PRIVATE_KEY to GITLAB_PRIVATE_KEY on this occasion, because it contains a private key that was generated exclusively for this use case. The according public key has been added as a deploy key in GitLab to all repositories that this repository needs access to. Add more detailed documentation concerning this configurationdirectly in the gitlab-ci files. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e948f5d manifest: check if docker build folder is empty BCS DevOps-000035 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ab318978 CI: integrate_into_manifest: Fix integration for recipes in SRCREV file -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@976aaec9 CI: deploy_gitlab_ci: Fix merge, integration branch was used after delete -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@65c6f273 CI: Rename foobar to ci-test, like the job names -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@60c311ab CI: Reuse existing integration branch preserving manual changes -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3318487d CI: integrate_into_manifest: Fix bug introduced when splitting functions -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4c74c580 CI: disable 'check' job for gitlab-ci integration as integrate is already disabled -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5d1fb5c4 CI: Enable MR pipeline for integration of gitlab-ci again Our settings refuse to merge if no pipeline has been run. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@69d604a4 CI: Fix merge pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@31d6d7da CI: deploy_gitlab_ci: Rework the deployment of gitlab-ci into the child projects The deploy_gitlab_ci now creates the integration commit and branch in each passed subproject and create an integration commit in the manifest containing all these new revisions. A build is then triggered on this commit to test the functionality. Split the update_submodule functions to reuse them in different ways. Remove some previously used files. BCS 746-000740
-
- May 30, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@8a2a7480 Integrate gitlab-ci/fix-port-for-lava-tests and 1 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6fbbf338 CI: Add fake lava test to ci-test, reduce fetch depth in update submodule -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d820110c CI: Add variable containing the port for ssh access of the gitlab instance Our server installation uses port 4444 for ssh access. The lava tests didn't took this into account. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@4e2dfb52 Integrate gitlab-ci/rename-to-seconorth -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a06956de Rename layers to seconorth -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@31226d01 Integrate gitlab-ci/increase-timeout-for-infrastructure-jobs -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@67b0195a CI: Increase infrastructure timeout to 10min -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@cbf2703c Integrate gitlab-ci/fix-gitlab-ci-integration -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d2210b6 CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@2be68740 Integrate gitlab-ci/fix-gitlab-ci-integration and 6 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f09c66c CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c39166f CI: deploy-gitlab-ci: Don't stop integration when one project is already updated Prior to this change the integration stop when one of the projects had already the latest ref of gitlab-ci in to submodule. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@aaac8d1c changelog_generator: Use logging instead of print, fix black -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@79afb233 CI: Move changelog_generator to gitlab-ci project The script can also be run in the normal python container, so this slightly reduces the complexity. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@383a5aca Added qt-multi-screen-compositor to project list -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3e88ad8e buildfng: Moved the image and distro variables to global The image and distro for the buildfng job can now be set via global/external variables. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@751fc360 Improve CI documentation BCS 746-000636 -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@93a1a4c9 Integrate gitlab-ci/fix-reuse-of-outdated-integration-branch and 2 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bcb6076b CI: Add check if integration branch is on top of target branch before reusing it The integration branch was reused even if there where new commits on the target branch, which could lead into reverting some changes. This adds a check, if the existing integration branch is directly based on the target branch and deletes it if not. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b5e9be0 CI: Pull new changelog_generator image, add token to the call. BCS 746-000785 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968886c0 Update README.md: Add description on the gitlab-ci CI and how to deploy -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@379707f3 Integrate gitlab-ci/remove-dual-espresso-image-build and 5 more -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2b7ec90 CI: Remove build for dual espresso again The pipeline is not setup to build from different manifest and so on, and the dual_espresso manifest will probably go to a seperate repo to keep it private. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@b81d573a CI: Remove '--verbose' from deploy step -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1ebf70c manifest: Added manifest file selection to ci-test -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1285aad7 manifest: Added manifest file name to integration script BCS 746-000518 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc6d7858 build: Added DualEspresso -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0941262a layers: Added nogplv3 and dual-espresso layer to CI/CD
-
Tobias Kahlki authored
Switched the remote protocols for Yocto, OE and Qt to HTTPS.
-
Tobias Kahlki authored
Cloning of public repositories via SSH doesn't work. Switched to HTTPS to enable the public checkout.
-
- May 25, 2022
-
-
Tim Jaacks authored
-
- May 23, 2022
-
-
GitBot authored
-- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-guf-machine/-/commit/af6ef6f129576626f9a3d8cbed9dc0f1711a36bb README: Refactor Readme and add License info Move build instruction into the manifest. Add license information to the REAMDE.md. BCS 746-000657 BCS 746-000659 BCS 746-000780
-
GitBot authored
-- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-guf-distro/-/commit/a6a685456a562726f915213e8d69b535c5d4aaab network: Fix distrooverride for network: set mac address, removed networkd The distrooverride changed from guf to seconorth, but these recipes haven't been adapted yet and the syntax was not changed to the new.
-
GitBot authored
-- Commit: https://git.seco.com/seco-ne/yocto/layers/meta-guf-distro/-/commit/18e1dd6d2714eaacb5f5a29e364d3721eb5712a3 README: Refactor Readme and add License info Add license information to the REAMDE.md. BCS 746-000657 BCS 746-000659 BCS 746-000780
-