I am seeing the following error when testing on Sandbox.

I have gutted one run to do nothing (after cloning repo)

and to proceed with fdio-infra-shiplogs publisher.

As the output [0] shows, jenkins-log-archives-settings

config is not found:

10:44:31 ERROR: your Apache Maven build is setup to use a config with id jenkins-log-archives-settings but can not find the config

10:44:31 ERROR: Build step failed with exception

10:44:31 java.lang.IllegalStateException: your Apache Maven build is setup to use a config with id jenkins-log-archives-settings but can not find the config

10:44:31       at org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider.supplySettings(MvnSettingsProvider.java:74)

The corresponding job on main fd.io Jenkins

passes, console [1] log shows it manages:

15:27:24 using settings config with name jenkins-log-archive-settings

15:27:24 Replacing all maven server entries not found in credentials list is true

15:27:24 using global settings config with name global-settings

15:27:24 Replacing all maven server entries not found in credentials list is true

Looking around the Sandbox, I have found a different job run

(one and half day old) which has passed

(this step, failure to publish-site could be expected)

but console output [2] does not mention jenkins-log-archives-settings:

21:59:06 using global settings config with name global-settings

21:59:06 Replacing all maven server entries not found in credentials list is true

Is there some outdated setting on Sandbox you can fix?

Vratko.

[0] https://jenkins.fd.io/sandbox/job/vpp-csit-verify-hw-perf-master/26/console

[1] https://jenkins.fd.io/job/vpp-csit-verify-hw-perf-master/136/console

[2] https://jenkins.fd.io/sandbox/job/vpp-verify-master-ubuntu1604/7/console