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

Anchore plugin compatibility in context mode, report fails due to missing javascript and css

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      If Jenkins installation is configured to run with a context path (behind Apache), Anchore image scanner plugin complains about missing javascript and css files while loading the Anchore report from the build summary page. The issue is probably confined to rendering the report. Server side functionality for executing anchore toolchain and generating the data for reports may be working as expected

        Attachments

          Activity

          Hide
          swathigangisetty Swathi Gangisetty added a comment -

          Plan for reproducing the issue - Use Apache as a reverse proxy for Jenkins and configure the context path using the instructions on https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache. Yet to figure out how to do it if Jenkins master is running in a container. 

           

          Show
          swathigangisetty Swathi Gangisetty added a comment - Plan for reproducing the issue - Use Apache as a reverse proxy for Jenkins and configure the context path using the instructions on https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache . Yet to figure out how to do it if Jenkins master is running in a container.   
          Hide
          swathigangisetty Swathi Gangisetty added a comment - - edited

          Plugin (index.jelly) references to static files (javascript and css) are relative, changing them to absolute paths by prefixing them with resURL is a recommended practice - https://wiki.jenkins-ci.org/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins. The following commit may address this issue if it was caused by a failure to resolve paths. Need to confirm

          https://github.com/jenkinsci/anchore-container-scanner-plugin/commit/e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb

          commit e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb
          Author: Swathi Gangisetty <swathi@anchore.com>
          Date:   Wed Mar 22 13:32:33 2017 -0700
          
              Create absolute paths to static resources (css, js, images) using resURL prefix
          
              Signed-off-by: Swathi Gangisetty <swathi@anchore.com>
          
          Show
          swathigangisetty Swathi Gangisetty added a comment - - edited Plugin (index.jelly) references to static files (javascript and css) are relative, changing them to absolute paths by prefixing them with resURL is a recommended practice - https://wiki.jenkins-ci.org/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins.  The following commit may address this issue if it was caused by a failure to resolve paths. Need to confirm https://github.com/jenkinsci/anchore-container-scanner-plugin/commit/e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb commit e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb Author: Swathi Gangisetty <swathi@anchore.com> Date: Wed Mar 22 13:32:33 2017 -0700 Create absolute paths to static resources (css, js, images) using resURL prefix Signed-off-by: Swathi Gangisetty <swathi@anchore.com>
          Hide
          swathigangisetty Swathi Gangisetty added a comment -

          Closing the ticket as the issue cannot be reproduced after the above commit

          Show
          swathigangisetty Swathi Gangisetty added a comment - Closing the ticket as the issue cannot be reproduced after the above commit

            People

            Assignee:
            swathigangisetty Swathi Gangisetty
            Reporter:
            swathigangisetty Swathi Gangisetty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: