[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-60179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60179  
 
 
  Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203139.1573802819000.10733.1576619700270%40Atlassian.JIRA.

[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty edited a comment on  JENKINS-60179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
 Fixed in release v1.0.21 by [PR| [ https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8] ]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203139.1573802819000.10729.1576619640178%40Atlassian.JIRA.

[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty edited a comment on  JENKINS-60179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
 Fixed in release v1.0.21 by [ GitHub PR  8 |https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203139.1573802819000.10731.1576619640246%40Atlassian.JIRA.

[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-60179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in release v1.0.21 by [PR|https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8]  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60179  
 
 
  Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 v1.0.21  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-60179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
 Hello Fred Blaise, you are right about the use of the artifacts generated by the anchore plugin - its mainly to render the reports and the data format was what the good old anchore tool output (precursor to anchore engine and now almost deprecated). The plugin actually works off of the same data you get from anchore-cli --json option but mangles it in order to be compatible with the rendering aspect. We've been meaning to switch it to be consistent but haven't had a chance to get to it. I can put in a fix to generate additional artifacts with data in the same format as you'd expect from the api (or anchore-cli --json option). Does that work for you?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203139.1573802819000.2047.1573884360132%40Atlassian.JIRA.

[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60179  
 
 
  Plugin JSON format to match anchore-cli JSONs format   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203139.1573802819000.2045.1573883520262%40Atlassian.JIRA.

[JIRA] (JENKINS-57650) anchore plugin isn't respecting engineRetries

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Adam Chou, engineRetries is how long (in seconds) the plugin will wait for anchore engine to complete analysis. Technically, it's the number of polling attempts spaced at 1 second intervals. A polling attempt is where the plugin checks the status of the image analysis in anchore engine. So a value of 700 instructs the plugin to wait for 700 seconds or 11+ minutes for the image analysis to complete. If you expect the analysis to take longer, say 1 hour, bump engineRetries to 6000  Docs for engineRetries attribute in the plugin help are incorrect. It should be addressed in the next release  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57650  
 
 
  anchore plugin isn't respecting engineRetries   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

[JIRA] (JENKINS-57650) anchore plugin isn't respecting engineRetries

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57650  
 
 
  anchore plugin isn't respecting engineRetries   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199581.1558657756000.3309.1568397120288%40Atlassian.JIRA.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43075  
 
 
  Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180185.1490290276000.3306.1568397060127%40Atlassian.JIRA.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180185.1490290276000.3305.156839751%40Atlassian.JIRA.

[JIRA] (JENKINS-59063) anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59063  
 
 
  anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201422.1566551844000.3293.1568396700558%40Atlassian.JIRA.

[JIRA] (JENKINS-59063) anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-59063  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items   
 

  
 
 
 
 

 
 Hello Bernhard Kaszt, apologies for the late response. I think flagging the build as unstable is a good idea. Especially when anchore engine (policy check op) produces a warn result. I'll add this to our backlog for next release. If you've already made the changes to the plugin to do this, please submit a PR and I'd be happy to merge it in. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201422.1566551844000.3290.1568396700499%40Atlassian.JIRA.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing issue due to inactivity. Can be reopened if the user responds back to the last comment  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52969  
 
 
  java.lang.InterruptedException: sleep interrupted   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty started work on  JENKINS-52969  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52969  
 
 
  java.lang.InterruptedException: sleep interrupted   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-52969  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.InterruptedException: sleep interrupted   
 

  
 
 
 
 

 
 You are right about the anchore stage failing. Anchore plugin logs indicate that the plugin received an interrupt signal and bailed. I'm trying to figure out what/who triggered this interrupt signal in the first place. It sounds like you've ruled out another stage failing and triggering the interrupt. Another potential for termination would be a timeout if its enforced on the anchore plugin stage. I would need to look through the build console logs to investigate this further  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-52969  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.InterruptedException: sleep interrupted   
 

  
 
 
 
 

 
 I think failFast aborts all parallel stages when one of them reports a failure. Is there any chance a different stage has failed for some reason and caused the in-progress anchore-verification stage to abort? Console log for the pipeline build (not the anchore plugin) will probably contain more information about stage interrupts and the extraneous cause if any. Look for something like "Sending interrupt signal to process" and the logs around that.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-52969  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.InterruptedException: sleep interrupted   
 

  
 
 
 
 

 
 Ben Mathews, how is the anchore plugin invoked? And how often do you notice this failure? From the stack trace it looks like the thread executing the plugin was interrupted. I'm not sure by what at this point but some context around how the plugin was invoked might help dig into it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52681) Anchore plugin fails with JSON error

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-52681  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin fails with JSON error   
 

  
 
 
 
 

 
 Ben Mathews, looks like your setup has the most updated Jenkins plugin release but a really old version of anchore engine (0.1.10). Current anchore engine release version is 0.2.3. This matters since the Jenkins plugin uses API to interact with anchore engine. "Security" tab of the Anchore build report is a new plugin feature that queries the anchore engine for vulnerabilities and renders the results. In this case the API response to vulnerability listing from the anchore engine is not what the plugin expects and hence the error in anchoreplugin.log. You might want to consider upgrading anchore engine for the Security tab results in the Anchore report. However, this error should not impact the rendering of the Anchore report for the Jenkins build. The Anchore report should display a "Policy" tab that contains a summary and detailed policy evaluation results. Let us know if this is not the case.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Zoltan Medovarszky, the issue is fixed in anchore plugin version 1.0.14. Reports generated by previous plugin versions should be viewable with plugin version 1.0.14. Please give it a try and let us know if you see any errors  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from 

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty started work on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore report exception   
 

  
 
 
 
 

 
 Anchore plugin version 1.0.13 (or newer) should be backwards compatible for rendering reports generated by older plugin versions. If not, there's probably a bug in there somewhere. I'll be working on this issue and update the ticket with my findings. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore report exception   
 

  
 
 
 
 

 
 Zoltan Medovarszky, thanks for providing the detailed version information. Are you able to view the report with the anchore plugin version 1.0.14 and Jenkins 2.89.4?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore report exception   
 

  
 
 
 
 

 
 Zoltan Medovarszky, I see that you've listed the anchore plugin version as 1.0.13. Can you please confirm that the failed attempt to open the report resulted from anchore plugin version 1.0.13 or newer? I ask because version 1.0.13 removed the use of guava (com.google.common.collect.*) libraries but the stack trace in your description contains a reference to it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty edited a comment on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
 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]  {noformat}commit e365fe3772e47f4cdc624b63a2d5a2ad138d5fdbAuthor: Swathi Gangisetty Date:   Wed Mar 22 13:32:33 2017 -0700Create absolute paths to static resources (css, js, images) using resURL prefixSigned-off-by: Swathi Gangisetty {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
 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.  https://github.com/jenkinsci/anchore-container-scanner-plugin/commit/e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb 

 
commit e365fe3772e47f4cdc624b63a2d5a2ad138d5fdb
Author: Swathi Gangisetty 
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 
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
 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.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43075  
 
 
  Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Summary: 
 Anchore plugin compatibility in context mode, report  does not load  fails  due to missing _javascript_ and css   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report does not load due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty started work on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report does not load due to missing javascript and css

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43075  
 
 
  Anchore plugin compatibility in context mode, report does not load due to missing _javascript_ and css
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Swathi Gangisetty  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2017/Mar/23 5:31 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Swathi Gangisetty  
 

  
 
 
 
 

 
 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  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-43048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43048  
 
 
  Anchore report triggers datatables error if gate output contains only one row   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-43048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43048  
 
 
  Anchore report triggers datatables error if gate output contains only one row   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43048  
 
 
  Anchore report triggers datatables error if gate output contains only one row   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Attachment: 
 anchore-plugin-error.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty started work on  JENKINS-43048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43048  
 
 
  Anchore report triggers datatables error if gate output contains only one row   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Swathi Gangisetty  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2017/Mar/22 9:00 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Swathi Gangisetty  
 

  
 
 
 
 

 
 Anchore container image scanner plugin generates a report that can be accessed from the Jenkins build summary page. Navigating to Anchore Report page triggers error popups and the summary is missing 'Repo Tag' column (attached screenshot). The issue is observed when the output of gate evaluation contains only one row/entry for a given image.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
  

[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-41081  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Bug fix and other improvements to the plugin to be released in version v1.0.5, refer to the git commit above for the changes  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41081  
 
 
  Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 

[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-41081  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41081  
 
 
  Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty started work on  JENKINS-41081  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41081  
 
 
  Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Swathi Gangisetty  
 
 
Attachments: 
 screenshot-1.png, screenshot-2.png  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2017/Jan/13 11:56 PM  
 
 
Environment: 
 Jenkins version: 2.32.1  Anchore plugin version: 1.0.4  Jenkins running in a container  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Swathi Gangisetty  
 

  
 
 
 
 

 
 As per the help for "Policy file" parameter in the Anchore Container Image Scanner build step, the plugin uses a default policy if the field is left blank/empty. The actual behavior observed was the plugin evaluates the gate with an empty policy document resulting in no gate output   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment