[JIRA] (JENKINS-49620) Anchore report exception
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
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
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
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49620 Re: Anchore report exception Code changed in jenkins User: Swathi Gangisetty Path: src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreAction.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/cb2dd4c7aa111a2408e8c2185c2e5dd16423697c Log: Upgrade logic for handling type changes that doesn't trip findbugs Fixes JENKINS-49620 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-49620) Anchore report exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49620 Re: Anchore report exception Code changed in jenkins User: Swathi Gangisetty Path: src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreAction.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/7f06728ab3923abb8ca5dfd19a2e6dd7476edef3 Log: Upgrade logic for handling type changes that doesn't trip findbugs Fixes JENKINS-49620 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
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
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49620 Re: Anchore report exception Code changed in jenkins User: Swathi Gangisetty Path: src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreAction.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/90dd8cab1a6acdff9359fbd1f471b4cdb653c1f8 Log: Upgrade logic for handling type changes in report rendering class Fixes JENKINS-49620 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-49620) Anchore report exception
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
Title: Message Title Zoltan Medovarszky commented on JENKINS-49620 Re: Anchore report exception Swathi Gangisetty, no, I cannot open the reports with 1.0.14. These former reports were all generated with 1.0.12. The new reports generated with 1.0.14 just open fine. 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
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
Title: Message Title Zoltan Medovarszky commented on JENKINS-49620 Re: Anchore report exception Swathi Gangisetty, thank you for looking into it. I've just re-checked the stack trace and the build logs. The report was generated with an Anchore plugin version 1.0.12 Now we have 1.0.14 installed. The version of Jenkins was 2.73.3 before the upgrade. 18:09:46 2018-02-16T18:09:46.486 INFO AnchoreWorker Jenkins version: 2.73.3*18:09:46* 2018-02-16T18:09:46.486 INFO AnchoreWorker Anchore Container Image Scanner Plugin version: 1.0.12** 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
Title: Message Title Zoltan Medovarszky updated an issue Jenkins / JENKINS-49620 Anchore report exception Change By: Zoltan Medovarszky Environment: Jenkins LTS ver. 2.89.4, ubuntu:16.04Anchore version 1.0. 13 14 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
Title: Message Title
Zoltan Medovarszky edited a comment on JENKINS-49620
Re: Anchore report exception
[~swathigangisetty], thank you for looking into it.I've just re-checked the stack trace and the build logs.The report was generated with an Anchore plugin version 1.0.12Now we have 1.0.14 installed.The version of Jenkins was 2.73.3 before the upgrade. {{ *18:09:46* 2018-02-16T18:09:46.486 INFO AnchoreWorker Jenkins version: 2.73.3*18:09:46* 2018-02-16T18:09:46.486 INFO AnchoreWorker Anchore Container Image Scanner Plugin version: 1.0.12** }}
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
Title: Message Title
Zoltan Medovarszky updated an issue
Jenkins / JENKINS-49620
Anchore report exception
Change By:
Zoltan Medovarszky
After upgrade of Jenkins LTS to 2.89.4 the existing Anchore reports cannot be opened with exception: {{org.apache.commons.jelly.JellyTagException: jar: [ file:/opt/data/jenkins/var/lib/jenkins/plugins/anchore-container-scanner/WEB-INF/lib/anchore-container-scanner.jar!/com/anchore/jenkins/plugins/anchore/AnchoreAction/index.jelly:43:64: |file:///opt/data/jenkins/var/lib/jenkins/plugins/anchore-container-scanner/WEB-INF/lib/anchore-container-scanner.jar!/com/anchore/jenkins/plugins/anchore/AnchoreAction/index.jelly:43:64:] java.lang.NullPointerException}} \ { \ { at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)}} \ { \ { at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)}} \ { \ { at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)}} \ { \ { at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)}} \ { \ { at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)}} \ { \ { at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} \ { \ { at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)}} \ { \ { at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)}} \ { \ { at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)}} \ { \ { at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)}} \ { \ { at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)}} \ { \ { at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} \ { \ { at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} \ { \ { at org.kohsuke.stapler.jelly.ReallySta
[JIRA] (JENKINS-49620) Anchore report exception
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-49620) Anchore report exception
Title: Message Title Daniel Nurmi commented on JENKINS-49620 Re: Anchore report exception Hi Zoltan Medovarszky We are looking into the issue you've reported and will communicate progress here - from the description we're assuming that new jobs are rendering properly and the issue appears to be triggered when loading the reports for jobs that ran before the LTS upgrade <- if this is an incorrect assumption let us know! Best, -Dan 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
Title: Message Title
Zoltan Medovarszky created an issue
Jenkins / JENKINS-49620
Anchore report exception
Issue Type:
Bug
Assignee:
Daniel Nurmi
Components:
anchore-container-scanner-plugin
Created:
2018-02-19 10:41
Environment:
Jenkins LTS ver. 2.89.4, ubuntu:16.04 Anchore version 1.0.13
Priority:
Major
Reporter:
Zoltan Medovarszky
After upgrade of Jenkins LTS to 2.89.4 the existing Anchore reports cannot be opened with exception: org.apache.commons.jelly.JellyTagException: jar:file:/opt/data/jenkins/var/lib/jenkins/plugins/anchore-container-scanner/WEB-INF/lib/anchore-container-scanner.jar!/com/anchore/jenkins/plugins/anchore/AnchoreAction/index.jelly:43:64: java.lang.NullPointerException {{ at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)}} {{ at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)}} {{ at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}}
