Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7139

HtmlPublisher should be able to handle wildcard paths to find multiple html files

    Details

    • Similar Issues:

      Description

      I'm generating some HTML reports per module within my project, so they are in multiple directories, but I'd like to publish them all as one page with tabs to each file. So the ability to specify one path and a comma separated list of files doesn't quite work. I'd rather be able to do

      **\target\reports\fooTool*.html

      and have all found HTML files on the publish page, one tab each named for the file name being presented.

        Attachments

          Issue Links

            Activity

            Hide
            r2b2_nz Richard Bywater added a comment -

            Version 1.19 is out now (so should appear in update center soon). This adds ability for Ant style wildcards and hopefully should meet the requirements of this issue without the issue that happened in the previous implementation of it.

             

            Show
            r2b2_nz Richard Bywater added a comment - Version 1.19 is out now (so should appear in update center soon). This adds ability for Ant style wildcards and hopefully should meet the requirements of this issue without the issue that happened in the previous implementation of it.  
            Hide
            r2b2_nz Richard Bywater added a comment -

            Unfortunately once again this change has had to be backed out as it breaks people who don't run the jobs on the Jenkins master. It will be reintroduced soon hopefully once the code is tweaked to pick up the file from the right place so please hang tight

            Show
            r2b2_nz Richard Bywater added a comment - Unfortunately once again this change has had to be backed out as it breaks people who don't run the jobs on the Jenkins master. It will be reintroduced soon hopefully once the code is tweaked to pick up the file from the right place so please hang tight
            Hide
            bric3 Brice Dutheil added a comment - - edited

            In the meantime, you can write :

             

            script {
                def docFiles
                dir ('build/docs/asciidoc/') {
                    docFiles = findFiles glob: '**'
                }
                publishHTML target: [
                    allowMissing         : false,
                    alwaysLinkToLastBuild: false,
                    keepAll              : true,
                    reportDir            : 'build/docs/asciidoc/',
                    reportFiles          : docFiles.join(','),
                    reportName           : 'Documentation'
                ]
            }
            
            

             

             

            Show
            bric3 Brice Dutheil added a comment - - edited In the meantime, you can write :   script { def docFiles dir ( 'build/docs/asciidoc/' ) { docFiles = findFiles glob: '**' } publishHTML target: [ allowMissing : false , alwaysLinkToLastBuild: false , keepAll : true , reportDir : 'build/docs/asciidoc/' , reportFiles : docFiles.join( ',' ), reportName : 'Documentation' ] }    
            Hide
            r2b2_nz Richard Bywater added a comment -

            Hi everyone - I believe I now have a fix for the issue that caused the rollback and I have now produced a beta release which it would be good to get people to have a play with and see if it meets their needs. To get the beta release (1.22-beta-1) you'll need to set your Jenkins Update Centre URL to https://updates.jenkins.io/experimental/update-center.json as documented at https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/#using-the-experimental-update-center

            I've only just released the beta version so I'd imagine it might take up to 24 hours or so to show up in the update centre. Once you've had a play, it would be great if you could report back here on how you got on. If you have jobs that use the previous "normal" way you can test all the better as I'd really like to get some real usage info before releasing it publicly again.

            Thanks in advance

            Show
            r2b2_nz Richard Bywater added a comment - Hi everyone - I believe I now have a fix for the issue that caused the rollback and I have now produced a beta release which it would be good to get people to have a play with and see if it meets their needs. To get the beta release (1.22-beta-1) you'll need to set your Jenkins Update Centre URL to https://updates.jenkins.io/experimental/update-center.json  as documented at https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/#using-the-experimental-update-center I've only just released the beta version so I'd imagine it might take up to 24 hours or so to show up in the update centre. Once you've had a play, it would be great if you could report back here on how you got on. If you have jobs that use the previous "normal" way you can test all the better as I'd really like to get some real usage info before releasing it publicly again. Thanks in advance
            Hide
            stautz85 Sebastian added a comment -

            It works for me since two month with : */_report.html

            Show
            stautz85 Sebastian added a comment - It works for me since two month with : * / _report.html

              People

              • Assignee:
                r2b2_nz Richard Bywater
                Reporter:
                netappbluedevil NetAppBlueDevil
              • Votes:
                17 Vote for this issue
                Watchers:
                27 Start watching this issue

                Dates

                • Created:
                  Updated: