Feature #2423
closedmove osmo-gsm-tester jenkins builds to new split osmo-msc.git, osmo-bsc.git
100%
Description
Soon the new repositries resulting from the split-up of openbsc.git should have all the most recent changes (at first in the pre_release branches).
To test the new code state and also to ease jenkins SCM polling, move osmo-gsm-tester's jenkins build jobs to using the new repositries.
Updated by neels over 6 years ago
Since I started preparing the split, work on openbsc.git continued. Make sure that the most recent commits are also rebased into the new repositries.
Updated by neels over 6 years ago
- % Done changed from 0 to 20
openbsc.git up to and including 84b7e3723b8d7bf9bfd5db7ba5532c3d174c2c77 is now merged to osmo-msc.git and osmo-{bsc,mgw,sgsn}.git.
Updated by neels over 6 years ago
- Subject changed from move jenkins builds to new split osmo-msc.git, osmo-bsc.git to move osmo-gsm-tester jenkins builds to new split osmo-msc.git, osmo-bsc.git
Updated by neels over 6 years ago
- Status changed from New to In Progress
- % Done changed from 20 to 50
Added various build scripts to contrib and corresponding jobs on our jenkins:
osmo-gsm-tester_build-osmo-{bsc,mgw,stp,sgsn,ggsn}
-msc job already exists.
All of these binary build jobs run successfully.
Will still need to verify that the new jobs and new code work,
which is hard because of numerous failures on the rnd setup.
Adjusting to the new artifacts is on branch neels/test, to be submitted when tested successfully.
Updated by neels over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Using the new split repositories for the AoIP builds, the osmo-gsm-tester ran successfully for the first time in weeks:
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_run/2736/
This is using the debian 8 build node to build for the debian 8 osmo-gsm-tester production setup.
The https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-build-all/
builds all of those on debian 9 for the RnD setup which is on debian 9,
used when run with https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run-all/
At some point we can move the production setup to debian 9 and adjust the individual build jobs to use the deb9 build node.
This is after the deb9 builds on the RnD setup have run as successfully as the deb8 ones on prod,
and this shall be tracked in a different issue.
The production setup is using the new split osmo-{msc,bsc,sgsn,mgw,ggsn} repositories as of now. Yay!
