Need help debugging hudson.remoting.ChannelClosedException "channel is already closed" in Remoting (I have logs)

2018-02-01 Thread me
Hi all, I am trying to debug an intermittent failure with Remoting. I am familiar with the overall design of Remoting but not its implementation. I'm not sure if I should file a bug or not, so I am asking for help debugging here first. Please let me know if I should file a bug instead. Below I

Re: Plugin(s) for FPGA / Verilog development

2018-02-01 Thread martinda
Hi Derrick, I have used the plot plugin and the ACL report plugin (aka summary display plugin), but I have found them difficult to work with. In terms of log parsing (regex), I have thought of creating custom filter for logstash, run logstash from the command line, and get Jenkins to read the

Re: Chart.js does not work in Jenkins views due to conflict with (old) bundled prototype.js in Stapler

2018-02-01 Thread Ullrich Hafner
For the record if someone else tries to use Chart.js: https://github.com/jenkinsci/jenkins/pull/3277 https://issues.jenkins-ci.org/browse/JENKINS-49319 Workaround: replace

Re: Releasing CppNCSS plugin with JEP-200 compatibility fixes

2018-02-01 Thread Ullrich Hafner
+1 > Am 01.02.2018 um 17:24 schrieb slide : > > +1 for sure > > On Wednesday, January 31, 2018 at 12:30:25 AM UTC-7, Oleg Nenashev wrote: > Hi all, > > I want to release the new version of CppNCSS > plugin with a fix, which makes the

Re: Releasing CppNCSS plugin with JEP-200 compatibility fixes

2018-02-01 Thread slide
+1 for sure On Wednesday, January 31, 2018 at 12:30:25 AM UTC-7, Oleg Nenashev wrote: > > Hi all, > > I want to release the new version of CppNCSS > plugin with a fix, which makes the > plugin compatible with JEP-200 and resolves some other issues reported

Re: New release of CppCheck Plugin Needed

2018-02-01 Thread Jack Zylkin
I would not know what to do with ownership if I had it. I don't know how to build and release a version of a Jenkins plugin. Can you point me to instructions? Jack On Friday, January 26, 2018 at 12:59:27 PM UTC-5, Oleg Nenashev wrote: > > Hi Jack, > > The best way would be to take ownership

Re: Plugin(s) for FPGA / Verilog development

2018-02-01 Thread Ullrich Hafner
I think it makes sense to group all things together in a new plugin (or multiple). Otherwise the different results from the different plug-ins are not visible as a single result. You don’t need to extend from an existing one, most plugins provide extension points. E.g., the warnings plugin

Jenkins 2.89.4 LTS RC testing started

2018-02-01 Thread Oliver Gondža
Hello everyone, Latest LTS RC was made public and it is ready to be tested. Release is scheduled for 2018-02-14. Report your findings in this thread or on the test plan wiki page. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.89.4/jenkins.war Check community maintained LTS

Re: Plugin(s) for FPGA / Verilog development

2018-02-01 Thread Oleg Nenashev
Hi Derrick, It would be great to see that in open-source. I have previously implemented plugins for dozens of EDA tools at my previous jobs, but I was unable to get approvals to publish them. - My approach in OSS would be to create mini-plugins for each tool separately so they get