-
Bug
-
Resolution: Fixed
-
Major
When you publish more than one fitnesse xml results in this way (pipeline):
step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml'])
On a linux agent, if you go to FitNesse Results, you get the links for the two results and you can click on them to browse them.
The link resolves correctly to:
http://localhost:8080/job/MyJob/5/fitnesseReport/fitnesse_linux.xml
But on a Windows agent, the link points to a local disk folder as opposed to a http URL
C:\jenkins\workspaces\MyJob\fitnesseReport/fitnesse_linux.xml
This means that the link does not resolve when Jenkins is running (as expected) on a remote machine.
[JENKINS-58923] Cannot browse result of tests when publishing several fitnesse result files on Windows
I reproduced this on 1.28.
I could try again on 1.29 although it doesn't appear yet in my Jenkins as an available upgrade. My company stages these so this isn't going to be immediate. The change in 1.29 doesn't seem relevant though.
If that is relevant at all, we use Jenkins version 2.164.1
And to be complete, we use FitNesse version 20190628 to generate the xml files.
Below if my full pipeline that reproduces this (once the files are generated):
pipeline {
agent {
label 'windows-agent'
}
stages {
stage ('Repro') {
steps {
echo 'Make sure the files are in the Workspace'
}
}
}
post {
always {
step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml'])
}
}
}
Johann Moro
added a comment - - edited I reproduced this on 1.28.
I could try again on 1.29 although it doesn't appear yet in my Jenkins as an available upgrade. My company stages these so this isn't going to be immediate. The change in 1.29 doesn't seem relevant though.
If that is relevant at all, we use Jenkins version 2.164.1
And to be complete, we use FitNesse version 20190628 to generate the xml files.
Below if my full pipeline that reproduces this (once the files are generated):
pipeline {
agent {
label 'windows-agent'
}
stages {
stage ( 'Repro' ) {
steps {
echo 'Make sure the files are in the Workspace'
}
}
}
post {
always {
step([$class: 'FitnesseResultsRecorder' , fitnessePathToXmlResultsIn: 'fitnesse_*.xml' ])
}
}
}
Thanks johannmoro, I've been able to reproduce this one. It fails when master is linux and agent is windows. If both master and agent are windows, it works OK. I'll investigate into it.
Hi johannmoro, please could you provide which fitnesse-plugin version are you using? I haven't reproduce this one on my windows machine with ver. 1.29
Thanks!