Re: [PROPOSAL] Extract `hudson.node_monitors` in a new dedicated plugin

2016-01-12 Thread Oleg Nenashev
Definitely +1 if we keep it as a bundled plugin. What are we going too do with monitoring periodic works and NodeMonitor APIs? - We can leave them in the Core - We can move them into the plugin as well The second approach looks to be more generic since we suffer from performance

Re: Jenkins Code of Conduct

2016-01-12 Thread Oleg Nenashev
Maybe makes sense to just Governance meeting summaries to the mailing list. I mean the automatically generated log with decisions and TODOs пятница, 8 января 2016 г., 20:18:43 UTC+3 пользователь R Tyler Croy написал: > > > In case you don't regularly follow the Jenkins blog or twitter, we now >

Re: [Jenkins-events] Clarification on CIA program

2016-01-12 Thread Oleg Nenashev
Added the topic Jan 20th meeting agenda. Maybe we could shift the focus of this program. Or just close it, especially if we agree on press contacts topic. BR, Oleg воскресенье, 10 января 2016 г., 22:43:41 UTC+3 пользователь Oleg Nenashev написал: > > Added the developers ML to Cc. > > Maybe my

Re: Jenkins Code of Conduct

2016-01-12 Thread Christopher Orr
Yeah, I'm on a couple of other lists where the meeting links get posted to the list at the end. Looks like we have a volunteer, Oleg! :) On 12/01/16 14:39, Oleg Nenashev wrote: > Maybe makes sense to just Governance meeting summaries to the mailing list. > I mean the automatically generated log

Re: [Jenkins-events] Clarification on CIA program

2016-01-12 Thread Alyssa Tong
+1. good idea. On Tue, Jan 12, 2016 at 5:43 AM, Oleg Nenashev wrote: > Added the topic Jan 20th meeting agenda. > Maybe we could shift the focus of this program. Or just close it, > especially if we agree on press contacts topic. > > BR, Oleg > > воскресенье, 10 января

Re: [PROPOSAL] Split of `jenkins-test-harness` out of `jenkinsci/jenkins`

2016-01-12 Thread James Nord
Sounds good to me -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

[PROPOSAL] Extract `hudson.node_monitors` in a new dedicated plugin

2016-01-12 Thread Baptiste Mathus
Hi everyone, Some context: - In the past few days, I've been working on JENKINS-24278 to add inodes usage monitoring to Jenkins. That initially resulted in the creation of a new dedicated plugin

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-12 Thread Baptiste Mathus
Inline. Le 4 janv. 2016 3:31 PM, "Christopher Orr" a écrit : > > Hi all, > > > On 04 Jan 2016, at 12:03, Daniel Beck wrote: > > On 04.01.2016, at 11:29, Tomas Bjerre wrote: > >> I am also developing plugins for Stash/Bitbucket Server

Re: [PROPOSAL] Split of `jenkins-test-harness` out of `jenkinsci/jenkins`

2016-01-12 Thread Manuel Jesús Recena Soto
I always try to avoid big repositories. In this case, there are several reason to split it. +1 Maybe a good moment to review this page: https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test#UnitTest-Overview Regards, 2016-01-12 22:08 GMT+01:00 James Nord : > Sounds good