create feed of nightly builds of osmo-bts/osmo-pcu for sysmoBTS 1002 + 2050
Similar to the nightly Debian dpkg builds of libosmo*, OsmoNITB, OsmoSGSN* for x86/x86_64, we should
have a nightly opkg package feed of libosmo*, osmo-bts and osmo-pcu for the sysmoBTS 1002 and 2050.
This would make it easy for any users of such hardware to test current git master on their devices, without going through manual SDK builds.
#2 Updated by laforge almost 2 years ago
- Checklist item create build job to build the laforge/nightly branches added
- Checklist item create new FEED_URI for the nightly builds added
- Checklist item upload packages from build host to FEED_URI added
- Checklist item basic testing of current nightly build added
- Checklist item ensure we build and upload both sysmobts-v2 and sysmobts-2050 added
- Checklist item update user manual with information about how to use nightly builds added
- Checklist item check after some days if 'opkg upgrade' will actually update code as intended added
- % Done changed from 10 to 30
build has completed with current master of libosmo*, openbsc, osmo-bts and osmo-pcu. Related changes have been committed to meta-sysmocom-bsp and meta-telephony into the 'laforge/nightly' branch.
What's missing? See checklist.
#7 Updated by laforge over 1 year ago
- Checklist item deleted (
ensure we build and upload both sysmobts-v2 and sysmobts-2050)
- Assignee changed from laforge to dlsitzer
- % Done changed from 70 to 90
we don't actually do a separate sysmobts-2050 build anymore, we simply use the sysmobts-v2 builds on the 2050 these days. there are some manual steps that need to be executed after flashing, which we need to automatize.
Assigning to dlsitzer to test if opkg upgrade works on the nightly builds.
#8 Updated by lazlo over 1 year ago
I tested the 201310-testing firmware and the status is as follows
- image boots
- seen location updates form subscribers I've set up
- sent MO and MT SMS successfully
- made voice calls with FR codec - worked
- PCU (in combination with SGSN+GGSN) seems to have an issue (likely to be #1756) that made it not possible to have GPRS traffic. the problem was only identified by comparing the setup with the same system with 201310 firmware with the same config (where GPRS traffic was possible)