Skip to content
Success

#638 (Jun 30, 2026, 11:24:00 PM)

Started 6 hr 2 min ago
Took 3 min 28 sec on build4-deb12build-ansible
Build Artifacts
build.log156.30 KiB view
linux14.02 MiB view

Started by timer

This run spent:

  • 8 ms waiting;
  • 3 min 28 sec build duration;
  • 3 min 28 sec total from scheduled to completion.
Revision: 4bc9c1a7b413d00fb4e4c154b4259929bb44cba0
Repository: https://gerrit.osmocom.org/osmo-ci
  • origin/master
lint: 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
Oliver Smith at
jobs/{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
laforge at