The libosmocore commit aa00f99be2e4cc64ede20d8c9548b83054696581 adds a VTY item
that's missing a doc string, hence breaking the openbsc build (which actually
checks the doc strings unlike the libosmocore build job).
I pushed the fix I734b22c950242541322e902887bf779c14ba10fd and things should
light up "green" (aka blue) again.
BTW, in a RL discussion lynxis suggested that it would be good if libosmocore
commits were also checked against breaking openbsc. A point against it is that
often something in libosmocore is changed and requires a follow-up in openbsc
-- if the libosmocore build rejects commits that break openbsc, it would make
it impossible to get these changes in. The workaround could be to have a
secondary build job that merely comments on gerrit whether the openbsc build
still works, without having -V voting powers.
Anyway, so far I think it is sufficient to catch these hopefully few cases once
the regular master build on
jenkins.osmocore.org goes up red, like now.
~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte