[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Bernhard Kaszt commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container We also sometimes get the exactly same error. It often works, but randomly throws this error. And it's not clear why it fails then. There is no error message except that ssh-add failed to run. 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-54752) Ansi plugin fails to render formatted console output
Title: Message Title Bernhard Kaszt commented on JENKINS-54752 Re: Ansi plugin fails to render formatted console output We also get this error, the whole plugin is broken now since the last update :/ 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Bernhard Kaszt commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We have the same problem, running version 1.14.0 of the plugin. This error occurs every day and then we have to restart Jenkins to fix this. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Bernhard Kaszt commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Downgrade to 1.13.5 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Bernhard Kaszt commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Hello Ravi, I also noticed the same behavior on one of our builds jobs today. This bug with duplicate pods already existed in an older version of plugin and was already fixed I think. Updating this plugin is always a roller coaster ride 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Bernhard Kaszt commented on JENKINS-47501 Re: 2 pods are started instead of 1 after update to version 1.1 I think the problem was already fixed, now with the latest versions it's happening again... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-59063) anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items
Title: Message Title Bernhard Kaszt created an issue Jenkins / JENKINS-59063 anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items Issue Type: Improvement Assignee: Daniel Nurmi Components: anchore-container-scanner-plugin Created: 2019-08-23 09:17 Environment: Jenkins: 2.179 Anchore container scanner plugin: 1.0.19 Priority: Minor Reporter: Bernhard Kaszt With the option "Fail build on policy check STOP result" (bailOnFail), you can fail a build when it contains a "STOP" result". However right now, there is no way of marking a Jenkins build as "UNSTABLE", when there are warnings only in the docker image scan. For example I would like to give attention to the developers when there are medium leveled CVEs, but those should not fail the build. Suggestion: Make the build status for "WARN" items configurable. Add Comment
