Project

General

Profile

Bug #3338

master-osmo-gsm-manuals job fails to build

Added by laforge 11 days ago. Updated 11 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/13/2018
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

For some strange reason, the job https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-gsm-manuals/ failed to build from June 3rd onwards.

The failure is:

java.io.IOException: [ssh-agent] Could not find specified credentials

But what's even more odd than this: It wants to start the job on a deprecated debian8 slave:

Building remotely on @build2-deb8build-ansible@ (linux_amd64_debian8) in workspace /home/osmocom-build/jenkins/workspace/master-osmo-gsm-manuals

Where the job configuration clearly states it should be built on an "osmocom-master-debian9" label. The build2-deb8build-ansible node clearly doesn't have that label ?!? I'm a bit lost here.

History

#1 Updated by neels 11 days ago

for matrix builds jenkins often start the coordinating build on a completely unrelated build slave. That got me completely confused more than once, e.g. some gerrit verification builds being started on the osmo-gsm-tester APU. But it's only the orchestrator of the individual matrix builds which then again adhere to the slave selection. Since our jjb have this slave-axis thing, all of our builds are like this, IIUC.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)