Integrate...
Integrate gitlab-ci/CLEAOS-538-build-automatically-according-to-the-repository-on-which-mr-is-opened and 19 more -- Commit: clea-os/infrastructure/gitlab-ci@edb2b74d [PRE-BUILD] Introduce common preliminary job for repo init and sync * Right now each build job perform the same action of initialising repo. This approach is time and resource consuming, so we introduce a 'repo_checkout' job to perform repo init and sync actions. * The output of this job is stored as GitLab CI cache and pulled by each build job in the build stage. * Introduce 'allow_failure: false' condition for build jobs. * Minor fixes in build setup configuration. -- Commit: clea-os/infrastructure/gitlab-ci@d7308515 [BUILD] Define job to filter out unnecessary jobs from build pipeline * Introduce new job after the one generating build pipeline to filter out jobs from the generated 'build-pipeline.yml' file in case the build runs on a MR integration branch. * The automation script parses the .yml file and remove not necessary jobs. For instance, if a MR is opened in the 'meta-seco-imx' branch the filter excludes jobs regarding boards with CPU from other silicon vendors. * Introduce 'PROCESSOR' variable in job names in order to easy the filter out process. -- Commit: clea-os/infrastructure/gitlab-ci@5da68c19 [BSP][INTEGRATION][CICD] Added new subgroups "modules," "qualcomm," and "intel." We specify a more precise group path when accepting merge requests for layer integration. Refactored group path specification logic to simplify adding new BSP subgroups in the future. Added new BSP subgroups: "modules," "qualcomm," and "intel." -- Commit: clea-os/infrastructure/gitlab-ci@6172a7e1 [FIX][INTEGRATION][LAYERS] Set SECO_REMOTE devault value for layers The layers-integration pipeline fails to retrigger MR pipelines in the bsp group because the SECO_REMOTE variable is undefined. Set default value for SECO_REMOTE -- Commit: clea-os/infrastructure/gitlab-ci@3353ee7a [DEPLOY] Implement Custom files deployment -- Commit: clea-os/infrastructure/gitlab-ci@3ed0d141 [HW][SUPPORT] Add Santino SBC based on i.MX6 Solo and Dual Lite CPUs -- Commit: clea-os/infrastructure/gitlab-ci@12d0d7d2 [DOCKER] Hardcode the tag for clea-os-builder Docker image It follows the different tagging scheme, so might break if we change the CI_IMAGES_REV for images from gitlab registry -- Commit: clea-os/infrastructure/gitlab-ci@ca1a2d56 [DOCKER] Add variable for LAVA an Exein Docker images -- Commit: clea-os/infrastructure/gitlab-ci@91fe9a6d [DOCKER] Adopt new Docker images url scheme -- Commit: clea-os/infrastructure/gitlab-ci@d6cac3d1 [CHANGELOG] Adjust changelog filename for custom projects in the release -- Commit: clea-os/infrastructure/gitlab-ci@5b87d970 [FIX][TEST][RELEASE] fix in image update job and in custom release - The bmap files are not accessible from the custom project release pages, this is due to the fact that the access token appended to the links grants access to the "image" files. This commit fix that; - Delete the appended token in custom images links because another token is already added in the deploy stage, when the deploy_artifacts.sh script is called. -- Commit: clea-os/infrastructure/gitlab-ci@a4de07e9 [SDK] Implement Automatic SDK Build * Add build pipeline for SDK. * Introduce variable ARTIFACTS_PATH to separate path to artifacts for images and SDK. * Remove pathname.txt We detect artifacts path with ARTIFACTS_PATH now * Remove BUILD_DIR, BUILD_DIRECTORY and MACHINE from build task. * Adapt artifacts_name.sh, check_build_artifacts.sh, deploy_artifacts.sh, generate_report.sh to handle SDK artifacts as well. -- Commit: clea-os/infrastructure/gitlab-ci@abe5ca72 [NOTIFY] Fix in token expiration date calculation -- Commit: clea-os/infrastructure/gitlab-ci@3fc502e4 [TEST] Add correct name to LAVA devices for Clea OS Things testing -- Commit: clea-os/infrastructure/gitlab-ci@cc44bfe3 [EDGEHOG] This commit allows backward compatibility of custom projects * Since the Clea OS rebranding of the project some of the custom projects build are actually broken because they are still pointing to the old 'Edgehog OS' brand and the old 'edgehog' tagged recipes. * Extend the usage of the SECO_REMOTE variable in order to become as much as possible independent from the name of the Yocto project and allow backward compatibility. * This commit refers to Jira ticket: CLEAOS-442 -- Commit: clea-os/infrastructure/gitlab-ci@bb9b1058 [DEPLOY] Fix in filesystem extension handling * Extend FS_EXTENSION usage in all parts of the code requiring it * Remove unnecessary variables from .gitlab-ci.yml file (already defined in the common.yml file) * This commit is related to Jira issue: CLEAOS-454 -- Commit: clea-os/infrastructure/gitlab-ci@0e7e7345 [DEPLOY] Remove 'latest' tagged SW artifacts from deploy stage * All SW artifacts are now uniquely identified by the manifest commit SHA or Tag, so there is no necessity to have 'latest' tagged artifacts. * The Azure blob storage folder organization easily allows to retrieve the software artifacts without the necessity of having 'latest' tagged ones. * This commit refers to Jira issue: CLEAOS-433 -- Commit: clea-os/infrastructure/gitlab-ci@6994676d [DOCS] Update image format from 'svg' to 'jpg' This update is necessary since the same images are used for Clea OS docs at the following link: https://git-pages.seco.com/clea-os/docs/ -- Commit: clea-os/infrastructure/gitlab-ci@a8b93ddb [REBRANDING] Apply new brand: Clea OS All file, variables and "edgehog" (case sensitive) occurrences have been replaced with the new brand "Clea OS" in accordance with the newest naming convention. -- Commit: clea-os/infrastructure/gitlab-ci@f2c40bcc [RASPBERRY] Add support to Raspberry Pi 4 machine * The Raspberry Pi 4 machine only supports U-Boot in Edgehog Things distro, for this reason we introduce a check on the presence of U-Boot files and eventually not deploy the package in case no files are found. * At build time, we only check the number of U-Boot artifacts and give a warning if they are less than expected.
Please register or sign in to comment