[JIRA] (JENKINS-58523) Multiple invocations of dependencyCheckPublisher in one build don't show correct results
Title: Message Title Christoph Amshoff commented on JENKINS-58523 Re: Multiple invocations of dependencyCheckPublisher in one build don't show correct results There is another bad consequence of the issue: when risk gates are given, the DependencyCheckPublisher compares the current values of the second invocation with the values from first invocation of the previous build, which will constantly produce red/yellow build if the number of violations in first invocation is lower than in second... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200669.1563309781000.16321.1563530760100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58523) Multiple invocations of dependencyCheckPublisher in one build don't show correct results
Title: Message Title Christoph Amshoff created an issue Jenkins / JENKINS-58523 Multiple invocations of dependencyCheckPublisher in one build don't show correct results Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-16 20:43 Priority: Major Reporter: Christoph Amshoff We have a build pipeline that executes dependency-check-maven for two independant modules (services and ui), and both reports should be published as part of the build. When dependencyCheckPublisher is invoked twice in the pipeline, two actions are added to the build and the UI shows two (identical) "Dependency-Check" links in the sidebar. However, both are showing the same page, apparently those of the second invocation; the information for the first publisher call is not accessible. Behavior is the same, whether there are two calls of dependencyCheckPublisher step in the pipeline, or a single call with a pattern string that does match both report files. Add Comment
