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
Please register or sign in to comment