Re: [pipeline] publishHtml failed with file present

2016-07-20 Thread Antonio Muñiz
On Tue, Jul 12, 2016 at 8:08 PM, Jérôme Godbout wrote: > If I make my Jenkinsfile now, can I assume it will still work for any > Jenkins 2.x version? Just to give myself an idea of the API stability at > this point? I believe so. Backward compatibility is taken very seriously by Pipeline develop

Re: [pipeline] publishHtml failed with file present

2016-07-12 Thread Jérôme Godbout
Ok, thanks, get inline with what I observed. You say not the only step impacted, but how one fetch those name? any link to API or doc somewhere? I was lucky to find an example into the a plugin that showed it, but for other I'm a little lost to find those API naming (I'm totaly new to Groovy langua

Re: [pipeline] publishHtml failed with file present

2016-07-12 Thread Thomas Zoratto
Hi, this bug is already reported here : https://issues.jenkins-ci.org/browse/JENKINS-29711 publishHTML is not the only step impacted > Le 12 juil. 2016 à 18:15, jer...@bodycad.com a écrit : > > I think I found the solution on that page: >

Re: [pipeline] publishHtml failed with file present

2016-07-12 Thread jerome
I think I found the solution on that page: https://jenkins.io/blog/2016/07/01/html-publisher-plugin/ publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: true, reportDir: 'x64\\Release\\FailedTestResult\\', reportFiles: 'index.html', reportName: 'Failed Tests']) should be pu

[pipeline] publishHtml failed with file present

2016-07-12 Thread jerome
Hi, I'm trying this into my piple Jenkinsfile: publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: true, reportDir: 'x64\\Release\\FailedTestResult\\', reportFiles: 'index.html', reportName: 'Failed Tests']); The directory is there and the index.html file exist too at that