Integrate gitlab-ci/multiple-integration-pipelines and 19 more
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@051871d9 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@e9015366 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@8840fc7e 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@b50c9ace Print less important output in grey color -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1e3136cd deploy_gitlab_ci: remove hard-coded integration targets Get targets dynamically using the INTEGRATION variable instead. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@02683cc1 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@0efe0f89 Ignore __pycache__ in scripts directory -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@db4d1051 Refactoring: rename arguments for consistency -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@59ce0ad8 Remove hard coded project and branch variables MANIFEST_PROJECT, MASTER_BRANCH_MANIFEST, MASTER_BRANCH_PROJECT -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@68bd1200 Add rules for integration pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@02f90212 Improve log messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@cedc7c1d commit_and_push: do not pass branch Branch can be implicitly determined via the repo. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f462d140 Throw and catch exception if git push fails Using new function raise_if_error() of GitPython 3.1.25: https://gitpython.readthedocs.io/en/stable/tutorial.html#handling-remotes -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@892c12fe Create separate integration branches for each target branch This makes it possible to integrate a project branch into different branches of the same manifest project. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@77f767c1 Generate integration pipeline based on CI variable Evaluate the INTEGRATION variable to determine target project and branch for integration instead of using the hard-coded variables. For now this works only for a single integration per target project because the integration branch name does not include the target branch and hence would be identical when trying to integrate into multiple branches of the same project. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5c2defce CI: prepare to work also with renamed machine names lime seco-mx6 -- 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. -- 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. -- 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.
Please register or sign in to comment