Erratic build failure on ci.jenkins.io

[rbello]

Jenkins and plugins versions report

Sometimes the build on the ci.jenkins.io platform fails to collect unit test reports.

What Operating System are you using (both controller, and any agents involved in the problem)?

Agent: windows-11

Reproduction steps

1. The failed build has been triggered automatically after a PR into main branch: https://github.com/jenkinsci/devops-portal-plugin/runs/11791884279
2. The same build has been triggered manually and was a success: https://github.com/jenkinsci/devops-portal-plugin/runs/11818420150

Expected Results

The build should success
See: https://github.com/jenkinsci/devops-portal-plugin/runs/11818420150

Actual Results

The build failed.
See: https://github.com/jenkinsci/devops-portal-plugin/runs/11791884279

Error log:

[2023-03-06T13:27:33.128Z] [ERROR] Error executing Maven.
[2023-03-06T13:27:33.128Z] java.io.FileNotFoundException: The specified user settings file does not exist: C:\Jenkins\workspace\lugins_devops-portal-plugin_main\null


windows-11/Build (windows-11): error in 'junit' step

Error in junit step, with arguments **/target/surefire-reports/**/*.xml,**/target/failsafe-reports/**/*.xml,**/target/invoker-reports/**/*.xml.

No test report files were found. Configuration error?

Anything else?

[rbello]

Hi @NotMyFault,

Can you help me diagnose this error?
The behavior is quite random, I don't know if it's a problem in the plugin settings or a random error on the ci platform.

[NotMyFault]

Error in junit step, with arguments /target/surefire-reports//.xml,/target/failsafe-reports//.xml,/target/invoker-reports//*.xml.

This is a common error if something failed in the build pipeline at an earlier point, so that no test files could be generated.
Take a look at the full build output on ci.jenkins.io to see what's wrong.

In this particular case, the following error is at fault:

14:27:26  C:\Jenkins\workspace\lugins_devops-portal-plugin_main>mvn --batch-mode --show-version --errors --no-transfer-progress -s null --update-snapshots -Dmaven.repo.local=C:/Jenkins/workspace/lugins_devops-portal-plugin_main@tmp/m2repo -Dmaven.test.failure.ignore -Dspotbugs.failOnError=false -Dcheckstyle.failOnViolation=false -Dcheckstyle.failsOnError=false -Dset.changelist help:evaluate -Dexpression=changelist -Doutput=C:/Jenkins/workspace/lugins_devops-portal-plugin_main@tmp/changelist clean install 
14:27:26  -XX:G1ConcRefinementThreads=4 -XX:GCDrainStackTargetSize=64 -XX:InitialHeapSize=134200512 -XX:MaxHeapSize=2147208192 -XX:+PrintCommandLineFlags -XX:ReservedCodeCacheSize=251658240 -XX:+SegmentedCodeCache -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseG1GC -XX:-UseLargePagesIndividualAllocation 
14:27:27  Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
14:27:27  Maven home: C:\tools\apache-maven-3.9.0
14:27:27  Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: C:\openjdk-11
14:27:27  Default locale: en_US, platform encoding: UTF-8
14:27:27  OS name: "windows server 2019", version: "10.0", arch: "amd64", family: "windows"
14:27:33  [ERROR] Error executing Maven.
14:27:33  java.io.FileNotFoundException: The specified user settings file does not exist: C:\Jenkins\workspace\lugins_devops-portal-plugin_main\null
14:27:33      at org.apache.maven.cli.configuration.SettingsXmlConfigurationProcessor.process (SettingsXmlConfigurationProcessor.java:91)
14:27:33      at org.apache.maven.cli.MavenCli.configure (MavenCli.java:999)
14:27:33      at org.apache.maven.cli.MavenCli.loadCoreExtensions (MavenCli.java:654)
14:27:33      at org.apache.maven.cli.MavenCli.container (MavenCli.java:535)
14:27:33      at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:263)
14:27:33      at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
14:27:33      at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
14:27:33      at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
14:27:33      at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
14:27:33      at java.lang.reflect.Method.invoke (Method.java:566)
14:27:33      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
14:27:33      at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
14:27:33      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
14:27:33      at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
14:27:33  [Pipeline] }
14:27:33  [Pipeline] // withEnv
14:27:33  [Pipeline] junit
14:27:33  Recording test results
14:27:33  No test report files were found. Configuration error?

which was already resolved, so replaying the build should lead to a successful build.

[rbello]

which was already resolved, so replaying the build should lead to a successful build.

👍

Thank you for your reply @NotMyFault

[lemeurherve]

As @NotMyFault noted, the error you encountered has been resolved, sorry for the inconvenience.

For the record, here is the corresponding help desk issue: jenkins-infra/helpdesk#3424