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

HTML Reports in multi configuration job throwing 404 error

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • htmlpublisher-plugin
    • None

      Hi Team,
      I am creating a multi configuration job which runs multiple apps to check for app logs.As part of post build actions at the end of execution of each app a html report is generated. I would like to consolidate all the reports and display the link or the reports on the jenkins main page. I am using HTML publisher plugin for this task but i dont see my purpose solved as i can see few reports displaying 404 whereas the report is present.

      in current scenario i can see report tabs in all the config jobs but only few are populated and few throw 404.

      It so happens is that the last completed config alone has all the reports. Is there a way where i can display only the last completed task in the main page so that reports can be viewed from there. As a work around i have created a downstream job which displays all the reports in one place but would want the same be done in the main job itself rather than doing it on downstream job.

      Thanks

      Naresh.G

        1. html_report for multiconfig.PNG
          html_report for multiconfig.PNG
          17 kB
        2. multiconfig_view.PNG
          multiconfig_view.PNG
          18 kB

          [JENKINS-44069] HTML Reports in multi configuration job throwing 404 error

          mcrooney added a comment -

          Thanks for your report! To me this seems like intended behavior. Each "configuration" should run the publishers, so if each configuration is configured to publish more than that configuration generates, you'll run in to this problem. Otherwise you are asking HTML Publisher to ignore the fact that it is a multi-config and run once for all.

          I think best approaches would be to either configure each configuration to archive only the HTML Report it generates, and view them per-config, or do what you've done with a downstream job to aggregate them. What do you think? Is there any precedent for publishers which somehow ignore multi-config and just run once at the end of all of them?

          mcrooney added a comment - Thanks for your report! To me this seems like intended behavior. Each "configuration" should run the publishers, so if each configuration is configured to publish more than that configuration generates, you'll run in to this problem. Otherwise you are asking HTML Publisher to ignore the fact that it is a multi-config and run once for all. I think best approaches would be to either configure each configuration to archive only the HTML Report it generates, and view them per-config, or do what you've done with a downstream job to aggregate them. What do you think? Is there any precedent for publishers which somehow ignore multi-config and just run once at the end of all of them?

          Naresh G added a comment -

          Thanks Mcrooney

          I have made use of  a single downstream job for multiple upstream jobs, so that i dont have to create multiple downstream jobs for each multi config jobs.
          That way i am able to achieve consolidated reports of the multi config jobs.

          Naresh G added a comment - Thanks Mcrooney I have made use of  a single downstream job for multiple upstream jobs, so that i dont have to create multiple downstream jobs for each multi config jobs. That way i am able to achieve consolidated reports of the multi config jobs.

            mcrooney mcrooney
            nareshg4 Naresh G
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: