Re: Jenkins merging similar jobs into 1 job

Not a topic for the dev list. > On 28.09.2016, at 04:06, Erik Lovlein wrote: > > I see it explained here: https://issues.jenkins-ci.org/browse/JENKINS-25529 > > Daniel Beck added a comment - 2014/Nov/11 10:53 PM > The overall behavior is consistent with what Jenkins does

Re: Jenkins merging similar jobs into 1 job

I see it explained here: https://issues.jenkins-ci.org/browse/JENKINS-25529 Daniel Beck added a comment - 2014/Nov/11 10:53 PM The overall behavior is consistent with what Jenkins does independent of Build Flow; multiple

Does jenkins has global error handler?

Take a look at the stack trace supression plugin. /James -- 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: Someone to take over GHPRB

Well, my two cents is indeed to do things by the book in GitHub-land for the reasons that you mentioned (e.g., forks are still linked, etc.) But perhaps if that's going to be a protracted or painful process, it's worth reconsidering. On Tue, Sep 27, 2016 at 4:54 PM, Daniel Beck

Re: Someone to take over GHPRB

> On 27.09.2016, at 22:09, Ben Patterson wrote: > > It sounds good to me. FWIW I had submitted an issue to the 'current' parent > repo; I assume GH would only make the switch if all parties agree. Breaking the connection shouldn't need that -- we could delete the

Re: Someone to take over GHPRB

It sounds good to me. FWIW I had submitted an issue to the 'current' parent repo; I assume GH would only make the switch if all parties agree. FYI - https://github.com/janinko/ghprb/issues/443 On Tue, Sep 27, 2016 at 5:09 AM, Daniel Beck wrote: > > > On 26.09.2016, at 23:04,

Re: Adding pipeline compatabilty to jenkins plugin

On Tue, Sep 27, 2016 at 10:56 AM, Cédric Cousseran wrote: > Using a lowercase letter at the start of the function name did the trick Hmm, perhaps the Groovy parser uses letter case to disambiguate class names from function names in some cases. Never heard of that

Re: Minimum System Configuration required for efficient use of jenkins

Wrong mailing list. > On 27.09.2016, at 15:58, 'Ashvin Parmar' via Jenkins Developers > wrote: > > Hello all, > > I just want configuration requirement to run jenkins efficiently . > my requirements are > > 1.Minimum 20-30 projects runs simultaneously >

Re: Adding pipeline compatabilty to jenkins plugin

Please also add the pipeline script you used... Can be due to the fact you use string as the variable name and when it been serached it has some issues? Could you please upload your jelly view for this (If you have a github account to ease this - it will be great..) On Tuesday,

Minimum System Configuration required for efficient use of jenkins

Hello all, I just want configuration requirement to run jenkins efficiently . my requirements are 1.Minimum 20-30 projects runs simultaneously 2.daily minimum 10GB packages will be made in local server (should remain for 31 days in FIFO manner) and first time project building will be of more

Re: Adding pipeline compatabilty to jenkins plugin

Should not matter, but as a matter of convention, function names should start with a lowercase letter. -- 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

Re: Speeding up JenkinsRule tests?

On Mon, Sep 26, 2016 at 4:37 PM, Andrew Bayer wrote: > turning the JenkinsRule into a @ClassRule rather than a @Rule Be very, very careful. You can easily get yourself into trouble this way. -- You received this message because you are subscribed to the Google Groups

Re: Compatability with parallel

On Mon, Sep 26, 2016 at 11:53 AM, wrote: > I can't seem to pinpoint the exact issue when it crashes Without at least some information about the step you are writing and the script you are trying to demonstrate it with, it is hard to help. Narrow it down to a minimal

Re: Can't use sendkeys with Jenkins using Windows automated Snapin tool for Powershell

> On 27.09.2016, at 13:41, Jenkins Jimmy wrote: > > I doesn't seem to accept the sendkeys into the field. I know regular sendkeys > in powershell doesn't work with Jenkins, but I figured since WASP is for > automated testing that it would work. > > How can I get

Re: New Plugin hosting request: Splunk plugin for Jenkins

Hi Ted, Hosting requests are regularly reviewed by our team, but it can take a few days as it's done by volunteers. Daniel > On 27.09.2016, at 14:06, Ted Xiao wrote: > > I would like to request hosting the Splunk plugin >

New Plugin hosting request: Splunk plugin for Jenkins

I would like to request hosting the Splunk plugin https://wiki.jenkins-ci.org/display/JENKINS/Splunk+plugin+for+Jenkins Git repo: https://github.com/splunk/splunkforjenkins Jira ticket: https://issues.jenkins-ci.org/browse/HOSTING-201 License: MIT Thanks, Ted -- You received this message

Can't use sendkeys with Jenkins using Windows automated Snapin tool for Powershell

In the example below, I'm using WASP to try and use sendkeys with Jenkins. The following code input a min and max number into a random number generator and returns the results. Link to code: http://pastebin.com/cCGwyq3i My results return as follows: Minimum

Can't use sendkeys with Jenkins using Windows automated Snapin tool for Powershell

In the example below, I'm using WASP to try and use sendkeys with Jenkins. The following code input a min and max number into a random number generator and returns the results. Link to code: http://pastebin.com/cCGwyq3i My results return as follows: Minimum

Re: Someone to take over GHPRB

> On 26.09.2016, at 23:04, Ben Patterson wrote: > > Yeah breaking the fork link would be under the control of the other repo fwiw > so I couldn't promise that. I can ask GitHub support to do that if that's the consensus. -- You received this message because you are

Re: Adding pipeline compatabilty to jenkins plugin

Sure, here is the stack trace: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 3: unexpected token: dd3afb84-7f74-4a47-b9da-1cd5ed1cfc59 @ line 3, column 34. CustomStep 'dd3afb84-7f74-4a47-b9da-1cd5ed1cfc59'