updating OS to bullseye

[radsoulbeard]

The image ran on stretch (debian 9). Updating it to bullseye (debian 11)

[o-liver]

Looks good. Why are the infrastructure tests failing? Is it related to this change?

[srinikitha09]

LGTM

[srinikitha09]

Infrastructure tests are failing with the following error:

java.lang.ClassNotFoundException: edu.hm.hafner.analysis.parser.FindBugsParser at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1394) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1349) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1095) at java.base/java.lang.ClassLoader.loadClass(Unknown Source) Caused: java.lang.NoClassDefFoundError: edu/hm/hafner/analysis/parser/FindBugsParser at java.base/java.lang.Class.getDeclaredMethods0(Native Method) at java.base/java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.base/java.lang.Class.getMethodsRecursive(Unknown Source) at java.base/java.lang.Class.getMethod0(Unknown Source) at java.base/java.lang.Class.getMethod(Unknown Source) at hudson.model.Descriptor.<init>(Descriptor.java:304) at io.jenkins.plugins.analysis.core.model.Tool$ToolDescriptor.<init>(Tool.java:158) at io.jenkins.plugins.analysis.core.model.ReportScanningTool$ReportScanningToolDescriptor.<init>(ReportScanningTool.java:226) at io.jenkins.plugins.analysis.warnings.FindBugs$FindBugsDescriptor.<init>(FindBugs.java:103) at io.jenkins.plugins.analysis.warnings.FindBugs$FindBugsDescriptor.<init>(FindBugs.java:93) at io.jenkins.plugins.analysis.warnings.FindBugs$FindBugsDescriptor$$FastClassByGuice$$77668ca0.newInstance(<generated>) at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:569) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) Caused: com.google.inject.ProvisionException: Unable to provision, see the following errors:

Does anybody has any idea about this issue?

[rodibrin]

Does anybody has any idea about this issue?

Looks like SAP/jenkins-library#3058

[srinikitha09]

Does anybody has any idea about this issue?

Looks like SAP/jenkins-library#3058

Yes, exactly. How to overcome this? Any workaround?

[rodibrin]

Yes, exactly. How to overcome this? Any workaround?

no. we once removed the tests which were failing. Nobody dared to fix it (upgrade a package) since there were worries that the pipelines wouldn't work anymore.

[srinikitha09]

Yes, exactly. How to overcome this? Any workaround?

no. we once removed the tests which were failing. Nobody dared to fix it (upgrade a package) since there were worries that the pipelines wouldn't work anymore.

Are we allowed to ignore that job and merge the changes?

[srinikitha09]

As discussed with @radsoulbeard, ignoring infrastructure tests failure and merging the PR.