Feature #3203
closed
have jenkins build verification job
Added by laforge about 6 years ago.
Updated over 4 years ago.
Description
... right now all our build verification jobs are autotools based. We need to see how we can deal with cmake here, particularly if we want to build with -Werror and/or enable -fsanitize.
- Priority changed from Low to Normal
Status: In Progress
Done: 90%
Patches submitted:
steve-m: can you review/merge the osmo-fl2k patch?
EDIT: build ran fine with Werror, so I've enabled it in jenkins.sh.
- Status changed from New to Stalled
Waiting for steve-m to review/merge the osmo-fl2k.git patch. Afterwards I can update the osmo-ci.git patch, so it does not conflict anymore. Setting to stalled.
- % Done changed from 0 to 90
osmith wrote:
Waiting for steve-m to review/merge the osmo-fl2k.git patch. Afterwards I can update the osmo-ci.git patch, so it does not conflict anymore. Setting to stalled.
Sorry, I was not aware of the patch in Gerrit. Will merge it later today.
- Status changed from Stalled to In Progress
- Assignee changed from osmith to laforge
I just rebased the osmo-ci patch and merged it.
- Assignee changed from laforge to osmith
for some strange reason cmake cannot be found, despite all slaves having been updated with the new build container? Re-assigning to osmith.
I did not realize that the patch was already merged - thanks, Steve!
The osmo-ci.git patch had the old docker image hardcoded, that's why it could not find cmake. Fix in: https://gerrit.osmocom.org/c/osmo-ci/+/16399
Notably the script is really fast:
Took 3.4 sec on build2-deb9build-ansible
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Also available in: Atom
PDF
