Cellular Network Infrastructure » Core Network (CN) » OsmoGGSN (former OpenGGSN)

For some reason, the master-osmo-ggsn job is always building on the osmo-gsm-tester-rnd slave, instead of host2-deb9build-ansible like all other master builds. This is not intended and probably caused by a bug in jenkins, because this job is generated just like all others from master-builds.yml in osmo-ci.git, with the default "slave_axis" and without overriding it:

slave_axis: !!python/tuple [osmocom-master-debian9]

I've also looked at the job configuration with the jenkins UI, and the slaves are configured exactly the same, as with other master jobs, with just one label that is "osmocom-master-debian9". The build slave, where it always tries to run, osmo-gsm-tester-rnd, is not attached to that label, so this should not happen.

The job started to fail on October 1st, because then osmo-gsm-tester-rnd was not able to resolve git.osmocom.org anymore, therefore failed to clone the source of osmo-ggsn.

I've deleted the workspace on osmo-gsm-tester-rnd, maybe this resolves the problem already.

Right now I can't test whether it worked, because "Jenkins is going to shut down".