[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Johnson Qu resolved as Fixed Sorry that it's caused by Ngnix conf before Dependency-Track docker. I updated the size limited, so it resolved the issue. Thanks anyway. Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Johnson Qu Status: Reopened 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
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Johnson Qu reopened an issue Thanks Steve. I upgraded the plugin version to 1.3.2.1, but now I encountered another issue as below. [DependencyTrack] Publishing artifact to Dependency-Track [DependencyTrack] Could not connect to Dependency-Track. Received response code: 413 Request Entity Too Large Build step 'Publish results to Dependency-Track' changed build result to FAILURE Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Johnson Qu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett resolved as Fixed Thanks for reporting the issue. I've pushed an updated release which resolves this issue (and a few others). Version 3.1.2.1 will show up in the Jenkins update site in a few hours. Or it can be downloaded and manually installed without waiting for the update site to sync. https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-check-jenkins-plugin/3.1.2.1/dependency-check-jenkins-plugin-3.1.2.1.hpi Change log: https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Check+Plugin Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Steve Springett Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett started work on JENKINS-51053 Change By: Steve Springett 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-51053) Fail to publish Dependency-Track result
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51053 Re: Fail to publish Dependency-Track result Code changed in jenkins User: stevespringett Path: pom.xml src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyTrackPublisher.java src/main/webapp/help-dt-projectid.html http://jenkins-ci.org/commit/dependency-check-plugin/3776f5f1d591585634cbb295f624b5c41b701259 Log: Fix for JENKINS-51053. FilePath is accessible from master or slave. No need to force execution on slave. Simplified. Added verbage to doc regarding permissions. Updated version to 3.1.2.1 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Steve Springett Assignee: Steve Springett 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-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett commented on JENKINS-51053 Re: Fail to publish Dependency-Track result I've confirmed this to be a defect in the Jenkins plugin. Publishing works as expected when executing from the master node but fails with an NullPointerException when running from a slave. 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-51053) Fail to publish Dependency-Track result
Title: Message Title Johnson Qu created an issue Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2018-05-01 08:57 Environment: Jenkins 2.7.2 Dependency-Check Plugin 1.3.2 Java 1.8.1 Run from slave server Priority: Major Reporter: Johnson Qu [DependencyTrack] Publishing artifact to Dependency-Track ERROR: Build step failed with exception java.lang.NullPointerException at hudson.tasks.Publisher.getDescriptor(Publisher.java:122) at hudson.tasks.Recorder.getDescriptor(Recorder.java:51) at org.jenkinsci.plugins.DependencyCheck.DependencyTrackPublisher.getDescriptor(DependencyTrackPublisher.java:205) at org.jenkinsci.plugins.DependencyCheck.DependencyTrackPublisher.upload(DependencyTrackPublisher.java:167) at org.jenkinsci.plugins.DependencyCheck.DependencyTrackPublisher.access$100(DependencyTrackPublisher.java:56) at org.jenkinsci.plugins.DependencyCheck.DependencyTrackPublisher$1.call(DependencyTrackPublisher.java:120) at org.jenkinsci.plugins.DependencyCheck.DependencyTrackPublisher$1.call(DependencyTrackPublisher.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:181) at hudson.remoting.UserRequest.perform(UserRequest.java:52) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Thread.java:748) at ..remote call to JNLP4-connect connection from *..*./
