[JIRA] (JENKINS-51080) Custom WAR Packager - Support of Incremental releases (JEP-305)
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51080 Custom WAR Packager - Support of Incremental releases (JEP-305) Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-44229) Problem with Custom Tools plugin
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-44229 Problem with Custom Tools plugin Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-24114) Create a ToolVersionProvider extension point
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-24114 Create a ToolVersionProvider extension point Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-38783) Jobs waiting forever when http server not responding on custom tools request
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-38783 Jobs waiting forever when http server not responding on custom tools request Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-55376) Fix default date format to show time in console logs
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-55376 Fix default date format to show time in console logs Issue Type: Bug Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-01-02 09:31 Environment: The default date format for console logging displays months twice instead of showing minutes and doesn't display hours. Also adjusts the date format to be more in line with ISO 8601. Priority: Minor Reporter: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because
[JIRA] (JENKINS-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51229 Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Oleg Nenashev commented on JENKINS-51229 Re: Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information I do not plan to work on it anytime soon, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. Everybody is welcome to work on it 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-52692) Implement JEP-207: Introduce External Logging API in the Jenkins Core
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-52692 Implement JEP-207: Introduce External Logging API in the Jenkins Core Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-52692) Implement JEP-207: Introduce External Logging API in the Jenkins Core
Title: Message Title Oleg Nenashev commented on JENKINS-52692 Re: Implement JEP-207: Introduce External Logging API in the Jenkins Core https://github.com/jenkinsci/jenkins/pull/3575 addresses it, but I do not plan to work on it anytime soon. See https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context 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-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50718 append tool HOME to PATH in declarative Pipeline Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline No plan to work on this feature, I have marked the plugin for adoption. Dominik Bartholdi is it a Jenkins X-related feature request just in case? 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-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50219 Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log Change By: Oleg Nenashev Labels: newbie-friendly 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-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Oleg Nenashev commented on JENKINS-50219 Re: Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log I might be able to work on it at some point, but I will unassign it for now so that anybody else can pick it up and work on it 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-50219) Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50219 Jenkins agent windows service fails to restart with an unhandled COMException in WinSw's log Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-44129) Log file logger for Audit trail plugin leaks open file descriptors
Title: Message Title Pierre Beitz updated JENKINS-44129 Jenkins / JENKINS-44129 Log file logger for Audit trail plugin leaks open file descriptors Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed 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-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-47896 Jenkins core classes should implement SerializableOnlyOverRemoting Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-47458) Trilead-SSH2 fails with NPE when calling Connection#getReasonClosedCause()
Title: Message Title Oleg Nenashev updated JENKINS-47458 Jenkins / JENKINS-47458 Trilead-SSH2 fails with NPE when calling Connection#getReasonClosedCause() Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.157, TrileadSSH build-217-jenkins-14 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-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Oleg Nenashev stopped work on JENKINS-47896 Change By: Oleg Nenashev Status: In Progress Open 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-44229) Problem with Custom Tools plugin
Title: Message Title Oleg Nenashev commented on JENKINS-44229 Re: Problem with Custom Tools plugin I have marked the plugin for adoption recently, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. Unassigning so that anybody else can work on it. 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-52692) Implement JEP-207: Introduce External Logging API in the Jenkins Core
Title: Message Title Oleg Nenashev stopped work on JENKINS-52692 Change By: Oleg Nenashev Status: In Progress Open 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-54154) [Custom Tools Plugin] - JCasC compatibility
Title: Message Title Oleg Nenashev updated JENKINS-54154 Jenkins / JENKINS-54154 [Custom Tools Plugin] - JCasC compatibility Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Custom Tools Plugin 0.6 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-54154) [Custom Tools Plugin] - JCasC compatibility
Title: Message Title Oleg Nenashev commented on JENKINS-54154 Re: [Custom Tools Plugin] - JCasC compatibility Fixed by https://github.com/jenkinsci/custom-tools-plugin/commit/e2a47c840184ca753eb24983d9625645a822996b in Custom Tools Plugin 0.6 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-53566) /about/ does not reflect packaged overrides
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-53566 /about/ does not reflect packaged overrides Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Tibor Digana commented on JENKINS-54228 Re: xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Great job Nikolas Falco I will check it out on my Jenkins. 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-27157) Overriding Tool location(s) has no effect
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-27157 Overriding Tool location(s) has no effect Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-40782) Rooted path variables for tool home isn't treated as an absolute path
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-40782 Rooted path variables for tool home isn't treated as an absolute path Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-32682) Unable to use VERSION environment variable
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-32682 Unable to use VERSION environment variable Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-22183) Custom-tools plugin breaks environment for 'Execute Windows batch command'
Title: Message Title Oleg Nenashev assigned an issue to Unassigned I will have a really small bandwith in the community in the next months, see https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ for the context. I decided to mark this plugin for adoption and unassigned tickets so that anybody is welcome to take over the plugin and to become a maintainer. Some tickets already have pending pull requests which can be finalized. Jenkins / JENKINS-22183 Custom-tools plugin breaks environment for 'Execute Windows batch command' Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev commented on JENKINS-52695 Re: Update External Task API to natively support JCasC Some bits have been integrated into the code, so it should work now 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-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-52695 Update External Task API to natively support JCasC Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev stopped work on JENKINS-52695 Change By: Oleg Nenashev Status: In Progress Open 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-55376) Fix default date format to show time in console logs
Title: Message Title Pierre Beitz updated JENKINS-55376 Jenkins / JENKINS-55376 Fix default date format to show time in console logs Change By: Pierre Beitz Status: Open Fixed but Unreleased Resolution: Fixed 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-52873) Incrementalify External Logging API Plugins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-52873 Incrementalify External Logging API Plugins Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-52693) Create a reference External Logging implementation for Elasticsearch (based on Logstash Plugin)
Title: Message Title Oleg Nenashev resolved as Fixed https://github.com/jenkinsci/external-logging-elasticsearch-plugin Jenkins / JENKINS-52693 Create a reference External Logging implementation for Elasticsearch (based on Logstash Plugin) Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed 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-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-52695 Update External Task API to natively support JCasC Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-52695) Update External Task API to natively support JCasC
Title: Message Title Oleg Nenashev updated JENKINS-52695 Jenkins / JENKINS-52695 Update External Task API to natively support JCasC Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed 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-55375) Plugin not showing in update centre after release
Title: Message Title LambdaTest Automation created an issue Jenkins / JENKINS-55375 Plugin not showing in update centre after release Issue Type: Task Assignee: LambdaTest Automation Components: lambdatest-automation-plugin Created: 2019-01-02 08:09 Priority: Minor Reporter: LambdaTest Automation We have completed all the steps required to host our plugin and it successfully creates releases on jenkinsci repo. But still, we are unable to search it or view in the update center. Repo: https://github.com/jenkinsci/lambdatest-automation-plugin/ This is the first release of the plugin Add Comment
[JIRA] (JENKINS-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51998 Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-54925) Define basic test cases to automate
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54925 Define basic test cases to automate Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-38313 Re: External Build Log storage for Jenkins I have abandoned all tasks in this EPIC. As stated in https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ , Carlos Sanchez and Jesse Glick can take over any tasks, PRs and JEPs related to this EPIC 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-46300) pluginFirstClassLoader=true & adjunct fails to load resource
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-46300 pluginFirstClassLoader=true & adjunct fails to load resource Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-46300) pluginFirstClassLoader=true & adjunct fails to load resource
Title: Message Title Oleg Nenashev commented on JENKINS-46300 Re: pluginFirstClassLoader=true & adjunct fails to load resource I consider pluginFirstClassLoader=true as a hack, not as a feature which should be really used. Not sure why I was assigned here, but I have removed myself so that somebody else can take it if interested 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto edited a comment on JENKINS-55257 Re: Timestamper break builds on Windows agents For me this is happening on a Win 2012r2 agent, so it is not just Win2016. The Jenkins agent is running as administrator , I don't know of any with UAC or other privs changes, but I didn't deploy the servers set to never . 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-55315) Obtain target changelist from PerforceScm object in pipeline
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55315 Obtain target changelist from PerforceScm object in pipeline Change By: Karl Wirth Labels: P4_SUPPORT 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-52864) Cppcheck plugin fails to resolve files in details view
Title: Message Title
Mike Pumford edited a comment on JENKINS-52864
Re: Cppcheck plugin fails to resolve files in details view
While doing some jenkins updates I've now dug into this a little more deeply and I can now see exactly why the files are not being displayed. If I go to one of the summary view panes e.g.( cppcheckResult/source.all) I get an error like:{{Can't read file: /var/jenkins_home/jobs//jobs//workspace-files/ed57db50.tmp}}However if I go and look at the jenkins_home on the masterI can see that the path should actually be: \{{}} {{/var/jenkins_home/jobs//jobs//builds//workspace-files/ed57db50.tmp}} {{}} {{ }} So it just looks like the plugin is generating the wrong filesystem path( its missing the {{ builds/}} bit) and it has nothing to do with the difference in FS path between the jenkins master and the build slave as I get the same issue even if I make cppcheck produce workspace root relative paths for its errors using:{{-rp=$WORKSPACE}}In the cppcheck command line arguments.
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-52864) Cppcheck plugin fails to resolve files in details view
Title: Message Title
Mike Pumford edited a comment on JENKINS-52864
Re: Cppcheck plugin fails to resolve files in details view
While doing some jenkins updates I've now dug into this a little more deeply and I can now see exactly why the files are not being displayed. If I go to one of the summary view panes e.g.( cppcheckResult/source.all) I get an error like:{{Can't read file: /var/jenkins_home/jobs//jobs//workspace-files/ed57db50.tmp}}However if I go and look at the jenkins_home on the masterI can see that the path should actually be:{{/var/jenkins_home/jobs//jobs//builds//workspace-files/ed57db50.tmp}} {{ So it just looks like the plugin is generating the wrong filesystem path( its missing the {{ builds/}} bit) and it has nothing to do with the difference in FS path between the jenkins master and the build slave as I get the same issue even if I make cppcheck produce workspace root relative paths for its errors using:{{-rp=$WORKSPACE}}In the cppcheck command line arguments.
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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Roger Bernier assigned an issue to Roger Bernier Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Roger Bernier Assignee: Francisco Fernández Roger Bernier 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue updated an issue Jenkins / JENKINS-54746 Can't connect via SSH on 1.29.1 Change By: Darryl Pogue Attachment: config.xml 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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Abubadabu commented on JENKINS-45693 Re: Ability to decorate Pipeline builds as a global extension Hey Jesse Glick, any chance you can relese this feature? 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-53299) Cloud does not exist: kubernetes
Title: Message Title
Kyle McGovern commented on JENKINS-53299
Re: Cloud does not exist: kubernetes
Kevin Cai
podTemplate(label: label, cloud: 'myk8scluster', containers: [
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat')
]) {
}
You can specify the kube cloud name in your pod template. This is what Carlos Sanchez was referring to I believe.
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-49425) Average stage duration should not use failed builds on calculation
Title: Message Title Rodrigo Faria edited a comment on JENKINS-49425 Re: Average stage duration should not use failed builds on calculation There is already a more detailed similar issue on this subject about build times : JENKINS-21099 I guess the same algorithm should be applied to both build and stage estimations, so maybe this both issues should be executed together. 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-54746
Re: Can't connect via SSH on 1.29.1
I check the config.xml against the last version and it works so should be something related with the credential configuration, Could you attach the snippet related with the credential used by the Agents (in JENKINS_HOME/credentials.xml) ? remove the key and the passphrase if it has, I will replace them with other values. I need something like the following snippet{code} GLOBAL ayogo-build-agent-ssh ssh key USER {} {code}
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-53299) Cloud does not exist: kubernetes
Title: Message Title Carlos Sanchez updated JENKINS-53299 Jenkins / JENKINS-53299 Cloud does not exist: kubernetes Change By: Carlos Sanchez Status: In Review Resolved 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-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe created an issue Jenkins / JENKINS-55381 Configuration-as-Code compatibility Issue Type: Improvement Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2019-01-02 18:55 Labels: jcasc-compatibility Priority: Minor Reporter: René Scheibe 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
[JIRA] (JENKINS-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-55381 Configuration-as-Code compatibility Change By: René Scheibe Environment: Jenkins 2.60.3configuration-as-code 1.4 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-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe started work on JENKINS-55381 Change By: René Scheibe Status: Open In Progress 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-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe assigned an issue to Oliver Gondža Jenkins / JENKINS-55381 Configuration-as-Code compatibility Change By: René Scheibe Assignee: René Scheibe Oliver Gondža 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-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe updated JENKINS-55381 Jenkins / JENKINS-55381 Configuration-as-Code compatibility Change By: René Scheibe Status: In Progress Review 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-55381) Configuration-as-Code compatibility
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-55381 Configuration-as-Code compatibility Change By: René Scheibe Assignee: Oliver Gondža René Scheibe 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-55370) Exception during the Jenkins startup
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-55370
Re: Exception during the Jenkins startup
Awesome! thank you very much for very quick response. > {quote} Please see answer [https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanIreducethefootprintofthedatabaseoftheJenkinsPipelineMavenPlugin?] {quote} By change do you have an example of init script to disable 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Vivek Pandey commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server Baptiste Mathus yes, Devin Nusbaum is already looking in to it. 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Evgeny Shepelyuk edited a comment on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Hello, I'm using latest {{1.17}} version of {{SSH Agent Plugin}} and still expirience the same issue.Although docker image has {{ssh-agent}} cmd line command inside - the socker socket is created under {{/tmp} so it's inaccesisble
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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Evgeny Shepelyuk edited a comment on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Hello, I'm using latest ` {{ 1.17 ` }} version of ` {{ SSH Agent Plugin ` }} and still expirience the same issue.Although docker image has ` {{ ssh-agent ` }} inside - the socker is created under ` {{ /tmp ` } so it's inaccesisble
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-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Vishal Khanna edited a comment on JENKINS-49102 Re: Add quote character to role pattern to avoid white spaces Made a PR for this ticket- [ https://github.com/jenkinsci/role-strategy-plugin/pull/50 ][cc [~oleg_nenashev]] 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-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Vishal Khanna updated JENKINS-49102 Jenkins / JENKINS-49102 Add quote character to role pattern to avoid white spaces Change By: Vishal Khanna Status: In Progress Review 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-55381) Configuration-as-Code compatibility
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-55381
Configuration-as-Code compatibility
Change By:
René Scheibe
The {{TestCrumbIssuer}} is not compatible with JCasC.That's quite confusing when implementing JCasC compatibility tests for other plugins and seeing this stacktrace.*Test*{code:java}import io.jenkins.plugins.casc.ConfigurationAsCode;import org.junit.Rule;import org.junit.Test;public class ConfigurationAsCodeTest {@Rulepublic JenkinsRule j = new JenkinsRule();@Testpublic void test() throws Exception {ConfigurationAsCode.get().export(System.out);}}{code} *Output*{code:java}plugins: sites: - id: "default"url: "http://localhost:44791/update-center.json"jenkins: agentProtocols: - "CLI-connect" - "CLI2-connect" - "JNLP-connect" - "JNLP2-connect" - "JNLP4-connect" - "Ping" crumbIssuer: "FAILED TO EXPORT hudson.model.Hudson#crumbIssuer: \nio.jenkins.plugins.casc.ConfiguratorException:\\ Cannot find configurator for type class org.jvnet.hudson.test.TestCrumbIssuer\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry$1.load(DefaultConfiguratorRegistry.java:97)\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry$1.load(DefaultConfiguratorRegistry.java:93)\n\\tat com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)\n\\tat com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)\n\\tat com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)\n\\tat com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)\n\t\at com.google.common.cache.LocalCache.get(LocalCache.java:3965)\n\tat com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)\n\\tat com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4829)\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry.lookupOrFail(DefaultConfiguratorRegistry.java:70)\n\\tat io.jenkins.plugins.casc.ConfigurationContext.lookupOrFail(ConfigurationContext.java:71)\n\\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:160)\n\\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:43)\n\\tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:196)\n\tat io.jenkins.plugins.casc.core.JenkinsConfigurator.describe(JenkinsConfigurator.java:83)\n\\tat io.jenkins.plugins.casc.core.JenkinsConfigurator.describe(JenkinsConfigurator.java:30)\n\\tat io.jenkins.plugins.casc.ConfigurationAsCode.export(ConfigurationAsCode.java:411)\n\\tat org.jvnet.hudson.test.ConfigurationAsCodeTest.test(ConfigurationAsCodeTest.java:14)\n\\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\\tat
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier commented on JENKINS-52017 Re: Metrics Plugin relies on un-exposed module API I filled a PR to track this. I tried to focus my solution on removing the reflection, as this is almost impossible with Java 9+ 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-54746
Re: Can't connect via SSH on 1.29.1
I check the config.xml against the last version and it works so should be something related with the credential configuration, Could you attach the snippet related with the credential used by the Agents? remove the key and the passphrase if it has, I will replace them with other values. I need something like the following snippet
"ssh-credentials@1.14">
GLOBAL
ayogo-build-agent-ssh
ssh key
USER
"com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$DirectEntryPrivateKeySource">
{}
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-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc commented on JENKINS-55370 Re: Exception during the Jenkins startup > but looks like we are spinning up the H2 database, > I guess it is going to take some resources on the server side, > is there anyway that we can disable this feature or disable by default and enabled only when required. anyways thanks a bunch for very quick fix on the exception. Please see answer https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanIreducethefootprintofthedatabaseoftheJenkinsPipelineMavenPlugin? 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Baptiste Mathus commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server Great thanks! 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Baptiste Mathus assigned an issue to Devin Nusbaum Jenkins / JENKINS-55356 Some workflow jobs fail after restart on Java 11 server Change By: Baptiste Mathus Assignee: Devin Nusbaum 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Baptiste Mathus started work on JENKINS-55356 Change By: Baptiste Mathus Status: Open In Progress 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55356
Some workflow jobs fail after restart on Java 11 server
Change By:
Mark Waite
While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a {code}jenkins-url/safeRestart{code} will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs.Build log output from the failed builds has included messages like (seems to be windows specific):{noformat}07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTestResuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’Ready to run at Fri Dec 28 07:48:49 MST 201807:48:49 Timeout set to expire in 17 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // node[Pipeline] }07:48:50 Failed in branch windows-8-2.150.1[Pipeline] // parallel[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: missing workspace C:\J\S\workspace\der_git-client-pipeline_beta-3.0 on coleen-pc2-ssh{noformat}and this (seems to fail on Windows and on Linux):{noformat}08:48:33 [INFO] [ hpi ]-Resuming build at Fri Dec 28 08:51:46 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ??Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Ready to run at Fri Dec 28 08:52:07 MST 201808:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // timeout[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // node[Pipeline] // timeout[Pipeline] }08:52:08 Failed in branch windows-8[Pipeline] }[Pipeline] // node[Pipeline] }08:52:08 Failed in branch windows-8-2.150.108:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-3af9d572[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }08:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-1ba13955[Pipeline] // node[Pipeline] }08:57:14 Failed in branch linux-8[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] //
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Mark Waite commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server Devin Nusbaum the link to the list of plugins is a list of plugin files committed to the git repository at the time I ran the test. The Pipeline job definitions are Git client plugin Git plugin Both those Jenkinsfile examples are buildPlugin with a few options. The second example includes a long definition of some PCT / ATH code that is not executed. 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-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Abubadabu edited a comment on JENKINS-45693 Re: Ability to decorate Pipeline builds as a global extension Hey [~jglick], any chance you can relese release this feature? 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-55379) add support for warnings-ng-plugin to DSL Plugin
Title: Message Title Ulli Hafner assigned an issue to Unassigned Is this something that needs to be done in the warnings-ng plugin? Or is the owner of the change the jobdsl plugin? Jenkins / JENKINS-55379 add support for warnings-ng-plugin to DSL Plugin Change By: Ulli Hafner Issue Type: Task Improvement Labels: job help - dsl-plugin warnings-ng-plugin wanted Assignee: Ulli Hafner 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Evgeny Shepelyuk commented on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Hello, I'm using latest `1.17` version of `SSH Agent Plugin` and still expirience the same issue. Although docker image has `ssh-agent` inside - the socker is created under `/tmp` so it's inaccesisble
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-55315) Obtain target changelist from PerforceScm object in pipeline
Title: Message Title Karl Wirth commented on JENKINS-55315 Re: Obtain target changelist from PerforceScm object in pipeline Hi Alisdair Robertson, Thanks for the suggestion. I can see that this would be useful so I will discuss with the developers. 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-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Vishal Khanna assigned an issue to Vishal Khanna Jenkins / JENKINS-49102 Add quote character to role pattern to avoid white spaces Change By: Vishal Khanna Assignee: Vishal Khanna 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-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Vishal Khanna started work on JENKINS-49102 Change By: Vishal Khanna Status: Open In Progress 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-49425) Average stage duration should not use failed builds on calculation
Title: Message Title Rodrigo Faria commented on JENKINS-49425 Re: Average stage duration should not use failed builds on calculation There is already a more detailed issue on this subject: JENKINS-21099 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-48850) Random java.io.IOException: Unexpected termination of the channel
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce It's been two months since any information was provided that might give hints on the cause or reproduction and we're no closer to having any verification that this is actually a code rather than environment issue. Nor whether the remoting-kafka-plugin helps. I'm going to close it out as Cannot Reproduce. If someone is able to provide additional information, please do and we can re-open it. Jenkins / JENKINS-48850 Random java.io.IOException: Unexpected termination of the channel Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Angelo Loria commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries Seeing this exact issue on Jenkins 2.150.1, Build Pipeline 1.5.8. Have a global library set up in one repo/configured under Global Configuration, and a multibranch job that polls a different repo for changes to specific branches. Upon committing anything to any file in the global library repo, the multibranch job is triggered. I've read every thread I can find on the issue but cannot figure out how to not have jobs triggered when committing changes to the global library repo. It's basically unusable at this point, as I can't continue to trigger all jobs over and over. 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log I'll attach a photo. It happens when I click on the links in the side bar, main section or the info icon. They lead to URLs of the form: http://server:8081/job/CUSTOMER_Market/159/javadoc/info or http://server:8081/job/CUSTOMER_Market/159/javadoc/ The root of the project actual Javadoc link works. Could the "Publish Javadoc" post build action be colliding with the warnings plugin? http://server:8081/job/CUSTOMER_Market/javadoc 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Michael Thompson Attachment: 2019-01-02_15-29-54.png 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-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title douglas knudsen commented on JENKINS-55328 Re: recordIssues and ScanForIssues in Pipeline get NPE Errors I see this as resolved, but I'm getting this error with no PMD in use at all. I have ALL PMD checks, old PMD plugin, and new recordIssues removed from my declarative Jekinsfile and see this right after the recordIssues step using androidLint is firing. I do have all the old analysis plugins installed on Jenkins as well as the new WarningsNG plugin, I have to migrate, eh? If this is not related to this change, I can cut a new issue. I am using WarningsNG 1.0.1 The step for recording AndroidLint report is the below and the report is generated in Jenkins too. recordIssues enabledForFailure: true, tools: [androidLint(pattern: 'Rewards/build/reports/lint-results*.xml')] Post stage [Pipeline] androidLint [android-lint] Collecting Android Lint files... [android-lint] Searching for all files in /Users/Shared/Jenkins/Home/jobs/mobileheros_multibranch/branches/feature-poc-.ujsndh.c-warnignsng/workspace that match the pattern Rewards/build/reports/lint-results*.xml [android-lint] Parsing 1 file in /Users/Shared/Jenkins/Home/jobs/mobileheros_multibranch/branches/feature-poc-.ujsndh.c-warnignsng/workspace [android-lint] Successfully parsed file /Users/Shared/Jenkins/Home/jobs/mobileheros_multibranch/branches/feature-poc-.ujsndh.c-warnignsng/workspace/Rewards/build/reports/lint-results-playStoreMockDebug.xml with 2 unique warnings and 0 duplicates. [Pipeline] recordIssues Error when executing always post condition: java.lang.IllegalArgumentException: No valid tool defined! You probably used the symbol 'pmd' in your tool definition. This symbol is also used in the PMD plugin. In this case you must use the symbol 'pmdParser' instead, see JENKINS-55328. The symbol 'pmd' can be used only if the PMD plugin is not installed. at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.ensureThatToolIsValid(IssuesRecorder.java:251) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:634) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:619) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [Pipeline] }
[JIRA] (JENKINS-55240) Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons
Title: Message Title
René Scheibe edited a comment on JENKINS-55240
Re: Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons
I am a bit confused - the {{TestCrumbIssuer}} contained in the issue title is not contained in the provided stacktrace. Why is that? I hit the same/similar problem with {{TestCrumbIssuer}} when testing for JCasC compatibility.Running {{ConfigurationAsCode.get().export(System.out)}} in tests results in the following output.*Jenkins Log*{code}0.262 [id=110] WARNING i.j.p.c.i.DefaultConfiguratorRegistry#internalLookup: Configuration-as-Code can't handle type class org.jvnet.hudson.test.TestCrumbIssuer{code}*JCasC Output*{code}plugins: sites: - id: "default"url: "http://localhost:38939/update-center.json"jenkins: agentProtocols: - "CLI-connect" - "CLI2-connect" - "JNLP-connect" - "JNLP2-connect" - "JNLP4-connect" - "Ping" crumbIssuer: "FAILED TO EXPORT hudson.model.Hudson#crumbIssuer: \nio.jenkins.plugins.casc.ConfiguratorException:\\ Cannot find configurator for type class org.jvnet.hudson.test.TestCrumbIssuer\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry$1.load(DefaultConfiguratorRegistry.java:97)\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry$1.load(DefaultConfiguratorRegistry.java:93)\n\\tat com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3524)\n\\tat com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2317)\n\\tat com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280)\n\\tat com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195)\n\t\at com.google.common.cache.LocalCache.get(LocalCache.java:3934)\n\tat com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3938)\n\\tat com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4821)\n\\tat io.jenkins.plugins.casc.impl.DefaultConfiguratorRegistry.lookupOrFail(DefaultConfiguratorRegistry.java:70)\n\\tat io.jenkins.plugins.casc.ConfigurationContext.lookupOrFail(ConfigurationContext.java:71)\n\\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:160)\n\\tat io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:43)\n\\tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:196)\n\tat io.jenkins.plugins.casc.core.JenkinsConfigurator.describe(JenkinsConfigurator.java:83)\n\\tat io.jenkins.plugins.casc.core.JenkinsConfigurator.describe(JenkinsConfigurator.java:30)\n\\tat io.jenkins.plugins.casc.ConfigurationAsCode.export(ConfigurationAsCode.java:411)\n\\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\\tat java.lang.reflect.Method.invoke(Method.java:498)\n\tat org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)\n\\tat groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)\n\tat groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)\n\\tat groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)\n\tat org.codehaus.groovy.runtime.InvokerHelper.invokePojoMethod(InvokerHelper.java:935)\n\\tat org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:926)\n\\tat
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Steve Prior commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Given the understandable lack of enthusiasm to keep automatic JDK installers up to date I'm wondering about another option. I'm planning to move my Jenkins install to run from a Docker container and there are repository images for OpenJDK's JDKs. Has anyone thought about the easiest way pull one of the OpenJDK images and then use that as a volume to attach to a Jenkins container? Then you'd simply configure jenkins to use the JDK in the given path and upgrading the JDK patch level would be about as simple as doing a pull for the updated image. The trick here is that you can use a Docker container as a volume, but not an image so you'd have to pull the image, create a container from it, then create the Jenkins container with that volume attached. 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-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati commented on JENKINS-55370 Re: Exception during the Jenkins startup Awesome! thank you very much for very quick response. > Please see answer https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanIreducethefootprintofthedatabaseoftheJenkinsPipelineMavenPlugin? By change do you have an example of init script to disable 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I think is related to SECURITY-440 changes, the use of ssh keys from files was deprecated due to a potential security leak os files, but I am not sure why it works with ssh-slaves 1.28.1 with the last versions of ssh-credentials and credentials. https://jenkins.io/security/advisory/2018-06-25/#SECURITY-440 https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L522-L529 https://github.com/jenkinsci/ssh-credentials-plugin/commit/18b3121fa94a174064447d637dc11539e33b3a76#diff-5b0528d739d5ca8914126dc568017ddd 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite commented on JENKINS-55356
Re: Some workflow jobs fail after restart on Java 11 server
When the 32 GB i5 machine failed, the message in the failing build log was similar to other Windows "workspace not found" messages:
14:31:36 [INFO]
Resuming build at Wed Jan 02 14:33:19 MST 2019 after Jenkins restart
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: ???
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: ???
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: ???
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: ???
Ready to run at Wed Jan 02 14:33:53 MST 2019
14:33:53 Timeout set to expire in 45 min
14:33:53 Timeout set to expire in 45 min
14:33:53 Timeout set to expire in 45 min
14:33:53 Timeout set to expire in 45 min
[Pipeline] }
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] // stage
[Pipeline] }
[Pipeline] }
[Pipeline] }
[Pipeline] // timeout
[Pipeline] // withEnv
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Archive (linux-8-2.150.1))
[Pipeline] }
[Pipeline] }
[Pipeline] junit
[Pipeline] // node
14:33:54 Recording test results
[Pipeline] // stage
[Pipeline] }
14:33:54 Failed in branch linux-8
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] }
14:33:55 Failed in branch windows-8-2.150.1
14:33:55 No test report files were found. Configuration error?
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] }
14:33:55 Failed in branch linux-8-2.150.1
Resuming build at Wed Jan 02 14:44:08 MST 2019 after Jenkins restart
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: ???
Waiting to resume part of Git Plugin Folder » Git Branches - Jenkinsfile (GitHub) » add-tag-action-test #10: Waiting for next available executor on ‘mark-pc4-ssh’
Ready to run at Wed Jan 02 14:44:29 MST 2019
14:44:29 Timeout set to expire in 35 min
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] }
14:44:29 Failed in branch windows-8
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
GitHub has been notified of this commit’s build result
Command Close created at
at hudson.remoting.Command.(Command.java:68)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1267)
at hudson.remoting.Channel$CloseCommand.(Channel.java:1265)
at hudson.remoting.Channel.close(Channel.java:1438)
at hudson.remoting.Channel.close(Channel.java:1405)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1272)
Caused: hudson.remoting.Channel$OrderlyShutdown
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to aws-ubuntu-18-a
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at hudson.remoting.Request.call(Request.java:202)
at hudson.remoting.Channel.call(Channel.java:956)
at hudson.FilePath.act(FilePath.java:1072)
at hudson.FilePath.act(FilePath.java:1061)
at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:144)
at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69)
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 Ivan Fernandez Calvo Sorry for the delay, had to wait 'til I was back in the office to grab the agent config. config.xml 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-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Progress Review 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-55379) add support for warnings-ng-plugin to DSL Plugin
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-55379
add support for warnings-ng-plugin to DSL Plugin
Change By:
Ulli Hafner
'warnings-ng-plugin' ([https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md|http://example.com/]) has no support for [ dsl-plugin ([ | https://jenkinsci.github.io/job-dsl-plugin/ #|http://example.com/ ] ) . Could you please add support to write those steps as a code in a Jenkins Job DSL pluging? I would like to convert this code with warning-ng-plugin support: {code:java}// Post-build actions publishers {checkstyle('myproject/build/reports/checkstyle/*.xml')findbugs('myproject/build/reports/findbugs/*.xml')pmd('myproject/build/reports/pmd/*.xml')tasks('**/*.java', '', 'FIXME', 'TODO', 'LOW', false)archiveJunit('myproject/build/test-results/test/TEST-*.xml'){ healthScaleFactor(0)} }{code}
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-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc updated JENKINS-55370 Delivered in 3.6.6 Jenkins / JENKINS-55370 Exception during the Jenkins startup Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed 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-55325) System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline
Title: Message Title Cyrille Le Clerc updated JENKINS-55325 Delivered in 3.6.6 Jenkins / JENKINS-55325 System scope Maven global settings.xml doesn't provide serverIds when using multibranch pipeline Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed 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-55336) Downstream pipeline trigger - optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
Title: Message Title Cyrille Le Clerc updated JENKINS-55336 Delivered in 3.6.6 Jenkins / JENKINS-55336 Downstream pipeline trigger - optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed 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-52864) Cppcheck plugin fails to resolve files in details view
Title: Message Title
Mike Pumford commented on JENKINS-52864
Re: Cppcheck plugin fails to resolve files in details view
While doing some jenkins updates I've now dug into this a little more deeply and I can now see exactly why the files are not being displayed. If I go to one of the summary view panes e.g.( cppcheckResult/source.all) I get an error like: Can't read file: /var/jenkins_home/jobs//jobs//workspace-files/ed57db50.tmp However if I go and look at the jenkins_home on the masterI can see that the path should actually be:{{}} /var/jenkins_home/jobs//jobs//builds//workspace-files/ed57db50.tmp{{}} }}So it just looks like the plugin is generating the wrong filesystem path( its missing the {{builds/ bit) and it has nothing to do with the difference in FS path between the jenkins master and the build slave as I get the same issue even if I make cppcheck produce workspace root relative paths for its errors using: {{ }}-rp=$WORKSPACE In the cppcheck command line arguments. {{}}
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-52864) Cppcheck plugin fails to resolve files in details view
Title: Message Title
Mike Pumford edited a comment on JENKINS-52864
Re: Cppcheck plugin fails to resolve files in details view
While doing some jenkins updates I've now dug into this a little more deeply and I can now see exactly why the files are not being displayed. If I go to one of the summary view panes e.g.( cppcheckResult/source.all) I get an error like:{{Can't read file: /var/jenkins_home/jobs//jobs//workspace-files/ed57db50.tmp}}However if I go and look at the jenkins_home on the masterI can see that the path should actually be: \ {{}}{{/var/jenkins_home/jobs//jobs//builds//workspace-files/ed57db50.tmp}}{{}}{{}}So it just looks like the plugin is generating the wrong filesystem path( its missing the {{builds/}} bit) and it has nothing to do with the difference in FS path between the jenkins master and the build slave as I get the same issue even if I make cppcheck produce workspace root relative paths for its errors using:{{ }}{{ -rp=$WORKSPACE}}In the cppcheck command line arguments. {{}}
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-55315) Obtain target changelist from PerforceScm object in pipeline
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-55315 Obtain target changelist from PerforceScm object in pipeline Change By: Karl Wirth Assignee: Karl Wirth 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.
