I have a declarative Jenkins pipeline that in a parallel stage runs the dependency check plugin. With their support <https://github.com/jeremylong/DependencyCheck/issues/1510#issuecomment-426219678> I have the plugin configured so that if a certain number of new vulnerabilities are detected it fails the build.
However, even though the build is marked as failed in Jenkins the pipeline is running on past that stage. So, the build is marked as failed *and* the artefact has been deployed into an environment! The plugin authors believe this is either the analysis plugin or Jenkins at fault. But I don't know how to investigate further. Can anyone here provide advice? Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f6971139-e1c9-4c63-ae97-fa608d66c6c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
