Cellular Network Infrastructure » Core Network (CN) » osmo-gbproxy

After rolling out Change-Id If4275cf3c8a5b70a67d742950a35ae8ead59a52e of osmo-ci.git, I was very surprised today to see https://jenkins.osmocom.org/jenkins/job/ttcn3-gbproxy-test-latest/21/display/redirect failing due to pulling from dockerhub.io.

To my extremely big surprise I discovered while debugging that this job is not created by our jenkins-job-builder descriptions, but it appears to be manually created? We had given up years ago on manually creating jobs exactly because they are much more maintainable in a git repo of jjb config files.