> Sorry for the screenshot.
> Anyways, I cannot really check if I have a symbolic link between those folders since I don't have the privilege to the VMs, which are hosting the Jenkins.
Crap, it's annoying. I will do some tests but i am pretty sure that it's something like this.
Even if it's not a very good practice I prefer to keep your bug report open, I don't think that the plugin should fail like this.
The version of Jenkins is 2.85, and I believe it's a Jenkins CLI thing. Don't be surprise of the old version . My project is using super old version of Jenkins and plugins, that's why I'm using pipeline-maven plugin 3.0.1.
I understand that too much ...
> Let's jump to the trial I did.
> After adding some additional options for withMaven(), it turned out the issue was resolved. I also tried to remove dir() or -f ./pom.xml as well, they all worked with only the additional options.
> Here's some of the log where it failed at release:perform
These additional stacktraces are helping a lot
In fact all publishers (it was JUnit in the screenshot, artifactsPublisher here) are calling XmlUtils.getPathInWorkspace
Thus they all have the same bug.
Looking at the code history it seems that Cyrille Le Clerc tried to fix it in the version 3.0.0 (ref
JENKINS-46084) but in your case the fix isn't working
The verification is done based on the /workspace/ folder which has to be found in both paths.
In the test we have
String workspace = "/var/lib/jenkins/workspace/testjob";
String absolutePath = "/app/Jenkins/home/workspace/testjob/pom.xml";
But in your environment you have something like
String workspace = "/var/lib/jenkins/workspace/IS-72660_generic_pipeline";
String absolutePath = "/data02/IS-72660_generic_pipeline/pom.xml";
And the "hack" used for
JENKINS-46084 doesn't work because in the absolute path you don't have a 'workspace' folder.
That's why I would love to understand how the server was configured (But I think that my idea of using symlink should be conform to what we see).
That's why you get the error :
Cannot relativize '/data02/IS-72660_generic_pipeline/pom.xml' relatively to '/var/lib/jenkins/workspace/IS-72660_generic_pipeline'
The workaround like you did is to disable the publishers for now.
I think the bug is reproducible and I could work on a fix with what you provided.
I just have to check with others developers if there is a "right" way to this in Jenkins today (it maybe evolved since Cyrille introduced it)
Any idea Félix Belzunce Arcos, Allan BURDAJEWICZ, Pierre Beitz ?