[JIRA] (JENKINS-57368) Syntax for inclusions and exclusions unclear
Title: Message Title Fly Cricket created an issue Jenkins / JENKINS-57368 Syntax for inclusions and exclusions unclear Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-05-08 10:40 Priority: Minor Reporter: Fly Cricket The syntax for multiple inclusions and exclusions is unclear ind the plugin itself, but also in the help. It cannot be found on https://wiki.jenkins.io/display/JENKINS/JaCoCo+Plugin either. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-55613) OWASP Dependency Check Plugin hangs forever
Title: Message Title Fly Cricket created an issue Jenkins / JENKINS-55613 OWASP Dependency Check Plugin hangs forever Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-01-16 07:51 Priority: Major Reporter: Fly Cricket Sometimes it happens that the OWASP Dependency Check Plugin starts and hangs forever. When this situation occurs the whole Jenkins Server is blocked. The hanging Job cannot be canceled via the Jenking UI. The Jenkins JVM has to be restarted. Building on master in workspace /.mntpts/sdb1/jenkins/jobs/NVD-UPDATE/workspace [DependencyCheck] OWASP Dependency-Check Plugin v4.0.2 [DependencyCheck] Executing Dependency-Check with the following options: [DependencyCheck] -name = NVD-UPDATE [DependencyCheck] -outputDirectory = /.mntpts/sdb1/jenkins/jobs/NVD-UPDATE/workspace [DependencyCheck] -dataDirectory = /.mntpts/sdb1/nvd [DependencyCheck] -dataMirroringType = none [DependencyCheck] -isQuickQueryTimestampEnabled = true [DependencyCheck] -jarAnalyzerEnabled = false [DependencyCheck] -nodePackageAnalyzerEnabled = false [DependencyCheck] -nodeAuditAnalyzerEnabled = false [DependencyCheck] -retireJsAnalyzerEnabled = true [DependencyCheck] -composerLockAnalyzerEnabled = false [DependencyCheck] -pythonDistributionAnalyzerEnabled = false [DependencyCheck] -pythonPackageAnalyzerEnabled = false [DependencyCheck] -rubyBundlerAuditAnalyzerEnabled = false [DependencyCheck] -rubyGemAnalyzerEnabled = false [DependencyCheck] -cocoaPodsAnalyzerEnabled = false [DependencyCheck] -swiftPackageManagerAnalyzerEnabled = false [DependencyCheck] -archiveAnalyzerEnabled = false [DependencyCheck] -assemblyAnalyzerEnabled = false [DependencyCheck] -msBuildProjectAnalyzerEnabled = false [DependencyCheck] -nuGetConfigAnalyzerEnabled = false [DependencyCheck] -nuspecAnalyzerEnabled = false [DependencyCheck] -centralAnalyzerEnabled = false [DependencyCheck] -nexusAnalyzerEnabled = false [DependencyCheck] -artifactoryAnalyzerEnabled = false
[JIRA] (JENKINS-27931) stdout/stderr are truncated even on failing test
Title: Message Title Fly Cricket commented on JENKINS-27931 Re: stdout/stderr are truncated even on failing test Same problem here. It does not make too much sense to hide the test's standard and error output. When using Gradle, the console log is also quite empty. So there's no workaround to get the desired information. 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-49038) Jenkins does not start due to a deadlock
Title: Message Title Fly Cricket commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock I've uploaded the HPI via the Jenkins GUI. Jenkins could be restarted without a deadlock. A second restart also worked. 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-49038) Jenkins does not start due to a deadlock
Title: Message Title Fly Cricket updated an issue Jenkins / JENKINS-49038 Jenkins does not start due to a deadlock Change By: Fly Cricket Attachment: claim-plugin-2.15.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-49038) Jenkins does not start due to a deadlock
Title: Message Title Fly Cricket commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock The issue is occuring everytime. 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.
