Re: Pipeline node scheduling options

On Friday, October 28, 2016 at 9:36:49 PM UTC-7, John Calsbeek wrote: > > > Shared storage is a potential option, yes, but the tasks in question are > currently not very fault-tolerant when it comes to network hitches. > Well, it would pay to make them more fault-tolerant :-) But even if you

Re: Pipeline node scheduling options

On Friday, October 28, 2016 at 9:14:53 PM UTC-7, Michael Lasevich wrote: > > Is there are way to reduce the need for tasks to run on same slave? I > suspect the issue is having data from the last run - if that is the case, > is there any shared storage solution that may reduce the time

Re: Pipeline node scheduling options

Is there are way to reduce the need for tasks to run on same slave? I suspect the issue is having data from the last run - if that is the case, is there any shared storage solution that may reduce the time difference? If you can reduce the need for binding tasks to specific nodes, you bypass

Re: I need to know Bundled Plugins version numbers for Jenkins 2.5

The version number are embedded inside the files. Unzip them to find out. On Friday, October 28, 2016 at 12:26:18 PM UTC-7, Robert Kruck wrote: > > For Jenkins 2.5 I know which are its bundled plugins by examining the > *.hpi files associated with Jenkins 2.5, but I don't know the versions of

I need to know Bundled Plugins version numbers for Jenkins 2.5

For Jenkins 2.5 I know which are its bundled plugins by examining the *.hpi files associated with Jenkins 2.5, but I don't know the versions of these plugins. I know there are scripts to find out bundled plugins' versions but I am not allowed to download them to my workplace computer. Does

pipeline loading error after upgrade to 2.19.1 LTS from 2.7.4 LTS

Hi, I have a pipeline code working on 2.7.4 LTS. After I upgraded to 2.19.1 LTS, it fails to load the pipeline script from git. I need some help in how to find the root cause of following failure: ... org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

Re: Best practices for develop/release branch model with pipeline

There are lots of answers to this and I am not going to pretend I know the "right" answer for you, but here are a few things you may want to consider when figuring things out: * In this "pipeline" of jobs you describe, only the initial build has access to the source repository - rest use

pipeline and warnings plugin

Hi, I still have problems using the warnings plugin for pipeline jobs. 1) I can not use pipeline syntax wizard. It simply crashes if I add the name of my file to scan (Scan workspace file) and get a java exception: javax.servlet.ServletException: java.lang.NullPointerException at

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

I dont understand. Last month the same scenary works succesfully. I didn't change anything in the Jenkins pipeline script.  El 28/10/2016 12:03 a. m., "Oscar Vadillo" escribió: > Thanks, but that's not the problem. The error appear only with the first > command line:

Re: Email-Ext and Pipeline Model Definition - How to send email notifications Culprits and Developers as recipients?

Email-ext needs access to the workspace, so if you don't use it inside a node, it won't work. On Fri, Oct 28, 2016, 07:11 Eddard wrote: > Hello i am trying to send email notification to relevant developers in > pipeline using model definition > with this: > > notifications

Email-Ext and Pipeline Model Definition - How to send email notifications Culprits and Developers as recipients?

Hello i am trying to send email notification to relevant developers in pipeline using model definition with this: notifications { always { emailext(body: 'Check console output at ${env.BUILD_URL} to view the results.', recipientProviders: [[$class:

Re: Best practices for develop/release branch model with pipeline

This is interesting, it's something I've been struggling with while converting our current system over to the new world (I really like the stage view!). We currently have a "pipeline" of freestyle jobs, that pass artifacts down the line. Build (and test) -> Deploy to stage -> Deploy to prod.

Re: Email-Ext and Pipeline - How to add Culprits and Developers as recipients?

Haven't this been implemented yet? I am getting Developers and Culprits through emailextrecipients final def recipients = emailextrecipients([ [$class: 'DevelopersRecipientProvider'], [$class: 'CulpritsRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider'],

Re: Email-Ext and Pipeline - How to add Culprits and Developers as recipients?

Same here Le jeudi 12 mai 2016 17:02:04 UTC+2, ludovic SMADJA a écrit : > > I add my cent to this feature, we also need it. > -- > > > Ludovic SMADJA > R engineer - build process and development > JALIOS SA > http://www.jalios.com > > > Le lundi 02 mai 2016 à 13:04 +, Slide a écrit : > >