Re: Pinned repositories on GitHub

On 2016-10-31 22:20, Baptiste Mathus wrote: remoting? I guess it's a pretty important one for Jenkins? :-) If anything, we should put there the most active repositories. I am not sure remoting and ATH fit into that category. (Presuming the point of pinning the repositories is to ease the

Re: Pinned repositories on GitHub

> On 01.11.2016, at 07:57, Oliver Gondža wrote: > > (Presuming the point of pinning the repositories is to ease the access for > developers, of course.) I haven't done this with this in mind, but rather showcase some important/popular ones. Established developers will

Re: maintainer requests

Hi, I've request write access for NodeJS+Plugin to resolve some issues. So is it a problem if we maintain toghether the NodeJS plugin? Il giorno venerdì 21 ottobre 2016 23:08:52 UTC+2, Greg Langston ha scritto: > > https://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin >

@Restricted do not prevent overall access to classes

Here is a particular use-case of access-modifier-checker we (or at least I) used to rely on for a long time: Declare a class that has to be public for some reason (jelly, stapler, @Extension, etc.) but prevent people from depending on its existence, its methods and fields. I have not

Re: maintainer requests

Thanks guys. Anything else you need from me to finalize? -- 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

Re: @Restricted do not prevent overall access to classes

I say it is a bug On Tuesday 1 November 2016, Oliver Gondža wrote: > Here is a particular use-case of access-modifier-checker we (or at least > I) used to rely on for a long time: Declare a class that has to be public > for some reason (jelly, stapler, @Extension, etc.) but

Re: @Restricted do not prevent overall access to classes

Sounds like there are some missing checks, for example here: https://github.com/kohsuke/access-modifier/blob/a3b787993a0f96543fdc122a51171540d2d37a7d/access-modifier-checker/src/main/java/org/kohsuke/accmod/impl/Checker.java#L253-L254 If you have noticed some lack of coverage, I would encourage

Re: True High Availability/load balancing for Jenkins. Its possible!!

HI Michael, I haven't actually tried putting it to production in any capacity. I think we have HA redis that I can use if this turns out to be a viable option. Its impossible to do anything 'production grade' with current Jenkins model of single point of failure. This I think is the biggest

Re: maintainer requests

> On 01.11.2016, at 12:58, Greg Langston wrote: > > Thanks guys. Anything else you need from me to finalize? I'd like to know which of the plugins you'd like to maintain since it looks like ECR would be co-maintained with Ivan, and NodeJS with Nikolas. -- You

Re: maintainer requests

I don't maintain NodeJS plugin, so feel free to take over 2016-11-01 18:39 GMT+01:00 Daniel Beck : > > > On 01.11.2016, at 12:58, Greg Langston wrote: > > > > Thanks guys. Anything else you need from me to finalize? > > I'd like to know which of the

Re: maintainer requests

> On 01.11.2016, at 18:57, nicolas de loof wrote: > > I don't maintain NodeJS plugin, so feel free to take over To clarify, Nikolas Falco who has also requested access. I didn't get your first name wrong ;-) -- You received this message because you are subscribed

Re: maintainer requests

oh, sorry for that, I'm used with typos on my name :P 2016-11-01 20:57 GMT+01:00 Daniel Beck : > > > On 01.11.2016, at 18:57, nicolas de loof > wrote: > > > > I don't maintain NodeJS plugin, so feel free to take over > > To clarify, Nikolas Falco who

Re: Embeddable Build Status Plugin

Anyway I can jump on this as well?? Have an outstanding PR that's been waiting for a while ... https://github.com/jenkinsci/embeddable-build-status-plugin/pull/18 :( On Monday, 15 February 2016 07:39:03 UTC-8, Antonio Muñiz wrote: > > Hello, > > Marius Gedminas (in CC), who seems to be the

Re: Questions on updating flowdock plugin to support pipeline

On Tue, Nov 1, 2016 at 2:04 PM, Tim Downey wrote: >if(build.getProject().getRootProject() != build.getProject()) { >projectName = > build.getProject().getRootProject().getDisplayName(); >configuration = " on " +

Why the Support Core Plug-in is known as a core plug-in?

Hi, Could you please let me know why Support Core Plug-in is said to be a "core" plug-in of Jenkins? What are the specific features needed for a plug-in to become a core plug-in. Thank you! -- *Minudika Malshan* Undergraduate Department of Computer Science and Engineering University of

Re: Why the Support Core Plug-in is known as a core plug-in?

We (CloudBees) have a plugin that we use to support our customers: cloudbees-support plugin. Some people may be concerned that it would be doing things unknown to their instance, so we released the core of this plugin (i.e. 99% of the code) as an open source plugin... being the core of our

Project actions (trend graphs) in pipeline jobs (SimpleBuildStep)

In https://github.com/jenkinsci/warnings-plugin/pull/80 Benjamin is trying to get the trend graphs of the warnings plug-in working for freestyle and pipeline jobs. It is almost working now, just one little thing: a trend graph (i.,e,. project action) is not shown for failed builds, see

Re: groovy script to get the jenkins jobs failures and there cause

Hi Rachel, Sorry for the delay response...thanks very much :) Regards, Naresh. On Friday, October 28, 2016 at 2:44:25 AM UTC+5:30, Rachel Moreno wrote: > > Hi Naresh, > > That's not a Jenkins question, but Groovy question. > > You're lucky, Christmas time is near ;) > > Try it with this code

Questions on updating flowdock plugin to support pipeline

Hi, I'm working on updating the Flowdock plugin to support pipeline and am getting hung up in how to map some of the old calls to the new API. In general, I've gone through and replaced AbstractProject with Run. I've got a few hangups that I was hoping that someone with direct knowledge