Feature #3765
closedBuild old (at least latest) releases of programs against "master of the day" libosmo*
100%
Description
As we've seen in issues like #3764, as well as in http://lists.osmocom.org/pipermail/openbsc/2019-January/012703.html - it is vital that we keep automatically building older applications against newer libraries. In fact, also older libraries like libosmo-{abis,netif,sccp} against libosmocore, as they require that.
This way we should catch at least the most blatant traps of incompatibilities, such as- namespace collisions
- semantic changes that make autotest fail
Related issues
Updated by osmith almost 5 years ago
- Status changed from New to In Progress
- Assignee changed from 118 to osmith
Updated by osmith almost 5 years ago
- % Done changed from 0 to 80
The script is implemented.
Patches submitted:
https://gerrit.osmocom.org/#/q/topic:build-old-tags-against-master
Jenkins job created:
https://jenkins.osmocom.org/jenkins/job/Osmocom-build-tags-against-master
I have configured it to default to the last three releases of each relevant repository. There is a bit of subtle breakage already, so I'm currently adjusting the configuration to not build the breaking releases (so the job runs through successfully). I'll list the broken ones here, so we can decide what to do with them.
Updated by osmith almost 5 years ago
- % Done changed from 80 to 90
Current result, from https://jenkins.osmocom.org/jenkins/job/Osmocom-build-tags-against-master/10/console:
Building old tags against libraries from current master... (ERR: new error, err: known error) * libosmo-abis 0.5.0 0.5.1 0.6.0 * libosmocore 0.12.1 1.0.0 1.0.1 * libosmo-netif 0.2.0 0.3.0 0.4.0 * libosmo-sccp 0.9.0 0.10.0 1.0.0 * openbsc 1.0.0 (err) 1.1.0 1.2.0 * osmo-bsc 1.2.1 (err) 1.3.0 1.4.0 (err) * osmo-bts 0.8.0 0.8.1 1.0.0 * osmo-ggsn 1.2.1 1.2.2 1.3.0 * osmo-hlr 0.2.0 0.2.1 1.0.0 * osmo-iuh 0.2.0 0.3.0 0.4.0 * osmo-mgw 1.3.0 (err) 1.4.0 (err) 1.5.0 * osmo-msc 1.2.0 1.3.0 (err) 1.3.1 * osmo-pcu 0.5.0 (err) 0.5.1 0.6.0 * osmo-sgsn 1.2.0 (err) 1.3.0 (err) 1.4.0 (err) * osmo-sip-connector 1.1.0 1.1.1 1.2.0 * osmo-trx 0.3.0 0.4.0 1.0.0
These are marked as known errors for now, because they fail for various reasons:
1. openbsc 1.0.0: testsuite
2. osmo-bsc 1.2.1: depends on libosmo-legacy-mgcp
3. osmo-bsc 1.4.0: testsuite
4. osmo-mgw: 1.3.0: testsuite
5. osmo-mgw: 1.4.0: testsuite
6. osmo-msc: 1.3.0: -Werror and deprecated gsm0480_create_ussd_release_complete()
7. osmo-pcu: 0.5.0: testsuite
8. osmo-sgsn 1.2.0: sgsn_test.c: gtp.h: No such file or directory
9. osmo-sgsn 1.3.0: testsuite
10. osmo-sgsn 1.4.0: testsuite
laforge and everybody else: how should we proceed with these?
Updated by osmith almost 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Patches were merged, the jenkins job is up and running now (and already failing, because of a new incompatibility). I'll create a follow up issue for the errors we're seeing.
Updated by osmith almost 5 years ago
- Related to Bug #3867: Some older Osmocom program releases don't build against current master libosmo* added