Project

General

Profile

Bug #4850

ttcn3-gbproxy-test* are not generated by jenkins-job-builder

Added by laforge 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
11/05/2020
Due date:
% Done:

100%

Spec Reference:

Description

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.


Related issues

Related to Core testing infrastructure - Bug #4839: docker.io sometimes returns EOF, breaking our buildsResolved11/02/2020

History

#1 Updated by laforge 3 months ago

  • Related to Bug #4839: docker.io sometimes returns EOF, breaking our builds added

#2 Updated by daniel 3 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

I did generate it through jjb, but seems I forgot to commit/push.

Should now be fixed with:
https://gerrit.osmocom.org/c/osmo-ci/+/21052

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)