mirrors/meta-arm
1
0
Fork 0
mirror of https://git.yoctoproject.org/meta-arm synced 2026-07-16 03:47:19 +00:00
Code Issues Projects Releases Wiki Activity

CI: add option to control whether warnings should be fatal or not

Browse Source 
Warnings being always fatal is quite anti-social because sometimes there
are temporary warnings that we don't want to break the CI.

Signed-off-by: Ross Burton <ross.burton@arm.com>
This commit is contained in:
Ross Burton
2026-06-16 16:51:10 +01:00
parent dea9d913d8
commit fe60f0804e
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitlab-ci.yml
+5 -1
View File
@@ -17,6 +17,8 @@ variables:
MIRROR_GHCR: ghcr.io MIRROR_GHCR: ghcr.io
# The list of extra Kas fragments to be used when building # The list of extra Kas fragments to be used when building
EXTRA_KAS_FILES: "" EXTRA_KAS_FILES: ""
# Whether warnings should be fatal (0/1)
FATAL_WARNINGS: 0
stages: stages:
- prep - prep
@@ -66,7 +68,9 @@ stages:
echo KASFILES=$KASFILES echo KASFILES=$KASFILES
kas dump --update --force-checkout --resolve-refs --resolve-env $KASFILES kas dump --update --force-checkout --resolve-refs --resolve-env $KASFILES
kas build $KASFILES kas build $KASFILES
./ci/check-warnings $KAS_BUILD_DIR/warnings.log if [ $FATAL_WARNINGS -ne 0 ]; then
./ci/check-warnings $KAS_BUILD_DIR/warnings.log
fi
kas shell ci/base.yml:lockfile.yml --command "$CI_PROJECT_DIR/ci/junit.sh $KAS_WORK_DIR/build" kas shell ci/base.yml:lockfile.yml --command "$CI_PROJECT_DIR/ci/junit.sh $KAS_WORK_DIR/build"
artifacts: artifacts:
name: "logs" name: "logs"