Issue

In the logs of my job, I can see a message like the one below:

[WARNING] [jenkins-event-spy] Unexpected Maven project file name 'NONSTANDARDNAME.xml', problems may occur

Environment

• CloudBees CI (CloudBees Core)
• CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
• CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Enterprise
• CloudBees Jenkins Enterprise - Managed controller
• CloudBees Jenkins Enterprise - Operations Center
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center
• CloudBees Jenkins Distribution
• Jenkins LTS

Explanation

This WARNNING message comes from jenkins-event-spy which belongs to pipeline-maven-plugin. AbstractMavenEventHandler.java doesn’t support non standard pom.xml file names which can cause trouble on your build.

Workarounds

• To get rid of this WARNING, you must use the standard name pom.xml instead of NONSTANDARDNAME.xmlfor your Maven project.
• Naming your pom.xml differently is not recommended. Nevertheless, if you really want not to rename your pom files and have a non-standard name, you could use a generic shell step sh without using the maven step withMaven. This way you would not be using the pipeline-maven plugin but calling local mvn commands inside your sh step instead.

Tested product/plugin versions

• Jenkins LTS 2.164.2
• Pipeline Maven plugin 3.7.1

References

• AbstractMavenEventHandler.java