- Mar 20, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bd7025b8 Manifest: run automatic pipeline on tags
-
- Mar 09, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@068749c7 Manifest build: add support for SSH_CONFIG variable
-
- Feb 28, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d67898a2 Manifest: skip build if "skip build" label is set -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bffc6097 Manifest: switch from branch pipelines to merge request pipelines This will make the manifest project support the "skip build" label. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5ba1ac68 Revert "Skip build if "skip build" label is set" This reverts commit 4db257d36052c74eabed7ef43a05d98d3998ffec. It does not work on the manifest, because we do not run merge request pipelines there, so CI_MERGE_REQUEST_LABELS is not set at all. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4db257d3 Skip build if "skip build" label is set
-
- Feb 20, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9d430fe8 Manifest integration: do not cancel previous pipelines on master -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8b08a083 Fix error handling on merge GitLab API has changed: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/94164/diffs#diff-content-c201dae00b72426693ddcb40edf6005e7702e935
-
- Feb 10, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a59a93a0 Package: Add needs to changelog, to package changelog also
-
- Feb 07, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8edbf2a6 Changelog generator: fix typo -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6ae06dd Changelog generator: pass projects as arguments Instead of hard-coding the project list in the changelog generator script, make them passable via arguments. This way we can have different changelogs in different envrionments. Hence we're adding the changelog job in the ci-test environment as well.
-
- Feb 06, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ed36b465 mirror_mr_pipeline: include pipeline-not-found message in output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5ee69ab9 mirror_mr_pipeline: fix error when no pipeline found This case should trigger a new pipeline instead of reporting an error.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e69d303e Changelog generator: remove debug output
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0264fe09 Changelog generator: get all merge requests This fixes older releases not appearing in the changelog.
-
- Jan 10, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c657f31f mirror_mr_pipeline: improve debug output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@473f12b1 mirror_mr_pipeline: add main call -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@88708b64 Convert CRLF to LF -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@169b2fa7 Improve mirroring MR pipeline Refactor three scripts into one in order to support triggering a new pipeline in the case of a skipped MR pipeline. This was not possible to implement with the previous three-script design. The single scripts were not used in other places anyway.
-
- Jan 09, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@897ba059 Manifest integration: remove dynamic job generation The dynamic job was only necessary because GitLab did not expand variables in the "trigger:project" keyword: https://gitlab.com/gitlab-org/gitlab/-/issues/347469 This has been fixed in GitLab 15.3, so we don't need it anymore: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92346
-
- Jan 03, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ea1f3bad cancel_pipelines: include downstream pipelines -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c8f97623 Add job to cancel outdated pipelines in merge requests Everytime we push a new commit to a branch, a new pipeline is created. Often the pipeline for the previous commit has not finished yet, and GitLab does not automatically cancel it. It consumes valuable build time, even if we don't need the results anymore. Adding a MR pipeline job to search for previous pipelines on the same branch and cancel them explicitly.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bab6f811 Package: move SDK files to subfolder "sdk" -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8bcaa426 scripts: Add delete_job_artifacts script to delete all artifacts from untagged jobs For a given project all artifacts may be deleted. This was needed due to space limitations on the gitlab server.
-
- Dec 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@28906544 Reduce artifact expiration of build jobs to 1 week
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d404f257 Alphaplan: allow failure on import Otherwise the parent pipeline is stuck in "running" state until the manual action has been performed. See for reference: https://gitlab.com/gitlab-org/gitlab/-/issues/361574 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dd2a6d7d Fix error message -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@04ac29ad CI-Test: fix deploy-files job -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@22c519f1 Move FTP jobs to FTP runner -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@84d0616b Add new deploy pipeline to Yocto -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0436868 Move reusable parts from CI-Test to common -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3d3b4d09 Yocto: fix SDK package -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@37360288 Yocto: fix SDK build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b6fc739 Package: add comment -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@95d6e368 alphaplan_fwr_import: add error handling -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@277d4af7 Package & deploy: do not allow missing dotenv file -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3c68ccab Alphaplan: add script for importing alphaplan data The script has mostly been copied from alphaplan_fwr.py, but with different input data. Adding a job to the CI-test environment for testing this. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b3238a1 Alphaplan: add script for generating alphaplan data This script has mostly been copied from alphaplan_fwr.py, but with different input data (artifacts from the SoftwareStore deploy job) and without actually importing the data to the Alphaplan database. Adding a job to the CI-test environment for testing this. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@387b8184 Deploy: save variables in deploy.env -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@902c9276 Deploy: save rsync file list for later stages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@15622149 CI-test: use caching between the pipeline stages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a96a923e CI-test: add deploy stages for SoftwareStore and FTP Rename all stages to uppercase on this occasion, since we're adding stages with names containing multiple words. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@056f1af1 Add package class and stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a1972724 Add script to query job logs filtered by status, tag, and log pattern -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d501fed4 Update isort config
-
- Nov 21, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9982711f Move deploy jobs to deploy runner
-
- Nov 11, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e48b4c0b package_release: Do not fail if a file does not exist
-
- Oct 18, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a5e27f6e FTP upload: Add flag to hide FTP upload stage This is a workaround to prevent customer releases being uploaded to our public FTP area. It should be removed as soon as we support uploading to different FTP target folders.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@543a2170 manifest_package: add release suffix Customer specific manifest projects can now set the RELEASE_SUFFIX variable, which then gets appended to the deployment folder names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c763c43f alphaplan_fwr: change variable "release_name_local" to "release_name" Otherwise it can be assumed that it might be correlated with outputdir_local, which is not the case. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d8d26a5 package_release: more refactoring - Make output-dir an argument that can be passed multiple times instead of hard-coding two dirs with certain meanings. - Remove LOCALDIR variable from package.env, because it is not used anywhere (only occurence was job class ".uploadsdkftp" which wasn't used anywhere either). -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc3698c8 package_release: refactoring Improve readability of package_release.py and its submodule generate_release_metadata.py. - Add describing comments throughout the file. - Remove duplicate code from functions. Simplify them, so that they do what their names say (and nothing more). - Rename variables and function arguments to make their purpose clearer. - Harmonize variable names with their corresponding command line arguments. - Add pydoc for functions. - Add type declarations to function arguments. - Generate MD5 and metadata files in the source directories so that they can be copied along with the rest of the files.
-
- Sep 27, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c831d1da get_integration_sources: check if CI is enabled Trying to query CI variables on a project which does not have the CI feature enabled leads to an HTTP 403 (forbidden) error. Check whether CI is enabled using the "jobs_enabled" flag.
-
- Sep 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e3dfaea CI:deploy: fix fngsystem deployment path The match to detect fngsystem still contained 'guf'. Changed to 'seco'. BCS 746-001043
-
- Sep 14, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f8d6de86 Make check error message more verbose -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@21e7edeb Improve ci-test build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@76bd81d8 Fix check job rules -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a6721243 Move check job to parent pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@593784e1 Refactor check_if_integration_branch_is_up_to_date - Use "source" and "target" terminology in the script, just like in the GitLab CI variables. - Spefify data types for function arguments. - Rename function arguments to better reflect their data types. - Move determination of integration branch into main function, so that the successfull status message can be more verbose. - Remove parent_merge_request feature and checking for gitlab-ci integrations, because the check job does not run on gitlab-ci integration branches at all. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@45b49ee3 Remove build stage on master We don't need to explicitly trigger a build after merging changes in gitlab-ci. A master pipeline on the target projects runs automatically.
-
- Sep 06, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a0f7e84f Rename pipeline stages to reflect YAML filenames
-
- Sep 05, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d25cdebf Really fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/manifest/-/jobs/129201
-
- Aug 31, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3eef782e deploy_gitlab_ci: integrate only correct projects into the manifest Previously we integrated all projects into the manifest, even those that belonged to a different manifest branch. That led to all manifests having the same project revisions, even if they should be different due to different intgrated project branches. Save a list of integration sources for each manifest branch separately now, so that we can check which project belongs to which manifest branch later. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b851ac6 Fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/127610 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c3fd0ecc Check if variable is defined before checking it value -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1be0f4b Fix jinja2 "or" operator -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8da534ec Run integration pipeline for target branch only When we're integrating a single branch into a single manifest branch, there is no need to run the intgeration pipeline for all configured integrations, but only for those that match the target branch of the current merge request. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8c94b725 ci-test: add job to check for correct foo branch This should catch an error where during a gitlab-ci merge process the wrong foo branch is integrated into the manifest, which happened in Yocto. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@163c7e1e Add yml extension to jinja2 templates -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@59523aa0 check job: disable verbose output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@28bf0065 retrigger: add job states to log message
-
- Aug 30, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fd742017 deploy_gitlab_ci: fix target branch in integration merge request We need to pass the correct target branch to the merge request creation instead of using the project's default branch. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@38379173 Run yamllint job on gitlab-ci integrations Otherwise no pipeline is created at all in these merge requests, which prevents the MR from being merged. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce4f8a3 changelog_generator: Fix machine project ID We have deleted the original project due to git corruption. Replace with the new project's ID. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a7aa7c26 deploy_gitlab_ci: fix project argument passing -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8a38f194 Put all manifest intgeration jobs into a single stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a09564c1 deploy_gitlab_ci: explicitly pass gitlab-ci project and branch -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@172e7625 Improve error messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0f5a370 Improve naming of functions and variables -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c8b484ca Retrigger MRs from all integrating projects Instead of getting the projects from the manifest file, search them via their INTEGRATION variable. Improve log messages on this occasion: print URL instead of just IDs. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e75bfc1 Deploy gitlab-ci to multiple branches Add different integration jobs for different manifest branches. The merge stage only has one job for each manifest, though, because otherwise we cannot guarantee a consistent state for all branches. Extend the deploy script for this purpose, so that it can deploy to multiple manifest branches at once. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@771dcff1 Fix temporary dir path We were passing the complete TemporaryDirectory object to the repo clone function instead of just the path string, resulting in the repo being cloned into a local dir "<TemporaryDirectory '/tmp/tmphwakypf8'>". Fix this to actually use the generated temp dir. This change makes it necessary to keep the TemporaryDirectory object reference until we don't need the directory anymore, otherwise it will be removed immediately. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce219c8 Print less important output in grey color -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e36261d deploy_gitlab_ci: remove hard-coded integration targets Get targets dynamically using the INTEGRATION variable instead. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@94cd6781 Recurse to child pipelines on retrigger This makes it possible to retrigger jobs that are not part of the given pipeline but in any nested child pipeline of it. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fb1219a7 Ignore __pycache__ in scripts directory -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0c29c995 Refactoring: rename arguments for consistency -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d461090b Remove hard coded project and branch variables MANIFEST_PROJECT, MASTER_BRANCH_MANIFEST, MASTER_BRANCH_PROJECT -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4aae414 Add rules for integration pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bfa38b24 Improve log messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1c9670d9 commit_and_push: do not pass branch Branch can be implicitly determined via the repo.
-
- Aug 02, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ef08f4ef deploy: Increase deploy timeout to 30min Especially when downloading the SDK the deploy takes longer than 10min. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@968aaadd build-jobs: Remove dump_install_command from buildsdk job When the dump_install_command script is executed in the SDK build step an error occurs because the fng-install script/vars are not available.
-
- Jul 13, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@52bae4a1 Lava Testreporting: Add script to generate markdown report for given jobids Adds scripts for mark down generation. Adds scripts for lava test result queries. Adds script to generate a mark down report from this data Call script from submit_test to generate a report directly after the testrun.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ab09db0b CI: Lava Test: Allow to install test image directly from gitlab The images from the build job can be directly installed from gitlab. To achive this some changes in the complete pipeline have been needed. 1. The variables used in the build job, like CI_PARAM_IMAGE, ... and related variables like BUILDPATH are only valid in the build job now. 2. The build job writes every variable needed in a follow up job into build.env. This also includes the url to the fng-install.sh of the final image. 3. The build.env file is used as dotenv artifact, as well as normal file artifact. The dotenv make the written variables automatically available in follow up jobs, that are using the aritfacts, like the deploy job. The normal file artifact is available via artifact download. (I did't found a way to download the dotenv file instead) 4. Some scripts have been added: - Find a job inside the pipeline by name, as the id is not known in advance. - Download all artifacts or one file of the artifacts from a given job - Download one file of the latest job by name 5. The scripts are used to download the build.env into the test job (where not artifacts are needed anymore) 6. The script is sourced and all variables are available inside the script. Additionally this adds a fake build job to the ci-test pipeline, that copies an image from srv73 and stores it as artifact in a way that a test-job can run on it, like in the normal yocto pipeline.
-
- Jul 12, 2022
-
-
GitBot authored
-- 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
-
- Jul 07, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system
-
- Jul 06, 2022
-
-
GitBot authored
-- 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.
-
GitBot authored
-- 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.
-
GitBot authored
-- 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.
-
- Jun 28, 2022
-
-
GitBot authored
-- 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.
-
GitBot authored
-- 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
-
- Jun 21, 2022
-
-
GitBot authored
-- 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
-
GitBot authored
-- 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.
-
- Jun 20, 2022
-
-
GitBot authored
-- 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.
-
-- 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
-