Started by timerEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.orgBRANCH_CImaster00552084392084391.0880208447006384bc9c1a7b413d00fb4e4c154b4259929bb44cba04bc9c1a7b413d00fb4e4c154b4259929bb44cba0origin/master4bc9c1a7b413d00fb4e4c154b4259929bb44cba04bc9c1a7b413d00fb4e4c154b4259929bb44cba0origin/master49644d8e48d658ce5bcd238a3fd42bf0e3b2da9170d44d8e48d658ce5bcd238a3fd42bf0e3b2da9170drefs/remotes/origin/osmith/wip44d8e48d658ce5bcd238a3fd42bf0e3b2da9170d44d8e48d658ce5bcd238a3fd42bf0e3b2da9170drefs/remotes/origin/osmith/wip4bc9c1a7b413d00fb4e4c154b4259929bb44cba04bc9c1a7b413d00fb4e4c154b4259929bb44cba0origin/masterhttps://gerrit.osmocom.org/osmo-cihttps://jenkins.osmocom.org/jenkins/job/build-kernel-torvalds/638/artifacthttps://jenkins.osmocom.org/jenkins/job/build-kernel-torvalds/changeshttps://jenkins.osmocom.org/jenkins/job/build-kernel-torvalds/638/https://jenkins.osmocom.org/jenkins/job/build-kernel-torvalds/638/testReportbuild.logbuild.logoutput/build.loglinuxlinuxoutput/linuxfalse#638208439200060build-kernel-torvalds #638638falsefalse638157121SUCCESS1782861840073https://jenkins.osmocom.org/jenkins/job/build-kernel-torvalds/638/build4-deb12build-ansible- lint/checkpatch/checkpatch_osmo.shaa9f25bc51178427bba4afb13710c2efaef0da2a1782739172000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.delint: ignore LINUX_VERSION_CODE
When running the linter against dahdi-linux.git or potentially other
repositories with out-of-tree linux kernel modules, it should not
complain about the LINUX_VERSION_CODE being used there:
> drivers/dahdi/dahdi-base.c:6397: WARNING:LINUX_VERSION_CODE:
> LINUX_VERSION_CODE should be avoided, code should be for the version to
> which it is merged
Change-Id: I82d64d43c04561b1643785cb71cfee92e513e560
2026-06-29 15:19:32 +0200aa9f25bc51178427bba4afb13710c2efaef0da2alint: ignore LINUX_VERSION_CODEeditlint/checkpatch/checkpatch_osmo.sh
- jobs/master-builds.ymljobs/gerrit-verifications.yml4bc9c1a7b413d00fb4e4c154b4259929bb44cba01782812065000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgjobs/{master,gerrit}: eim,ipa: wipe-workspace
Set wipe-workspace for the onomondo-eim and onomondo-ipa jobs to true,
so previous failures cannot influence new jenkins job runs. E.g.
currently we had gerrit-onomondo-ipa-build failing with:
+ mkdir build
mkdir: cannot create directory 'build': File exists
Most existing jobs call scripts/osmo-clean-workspace.sh from osmo-ci.git
at the beginning of their jenkins.sh instead of using wipe-workspace.
But this doesn't have any advantage here while making jenkins.sh more
complex. Let's use the built-in feature from jenkins here.
Change-Id: If4ef5ab804b05ad630cfa770741fe6053fdfb637
2026-06-30 09:34:25 +00004bc9c1a7b413d00fb4e4c154b4259929bb44cba0jobs/{master,gerrit}: eim,ipa: wipe-workspaceeditjobs/gerrit-verifications.ymleditjobs/master-builds.yml
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforgehttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith