Re: Restartable Pipeline stages

Just did. https://issues.jenkins-ci.org/browse/JENKINS-35989 On Tuesday, June 14, 2016 at 11:42:49 PM UTC-4, Rikesh Dhokia wrote: > > I too am looking for functionality like this. @Mark, did you create a > relevant JIRA issue for this? > > > > On Tuesday, 3 May 2016 03:23:07 UTC+10, Mark

Re: Email only after all retries fail

Try this: // You need some different default values so it won't be a null def retryCount = build.envVars['NAGINATOR_COUNT'] ?: 0 def retryMaxCount = build.envVars['NAGINATOR_MAXCOUNT'] ?: 1 retryCount == retryMaxCount On Monday, May 23, 2016 at 5:34:40 PM UTC+2, Илья Ефимов wrote: > > Hi. I

Re: PermGen errors on master and slave

In general, it's recommended to run the same JVM version on the master and the agents, mostly due to how remoting works I think (Oleg will correct me if wrong). And yes. PermGen was removed from the Java VM starting at Jdk 8. Cheers Le 14 juin 2016 9:40 AM, "Mike Emett"

Re: Jenkins shows no changes between a failed build (with changes) and the successful build that follows

I should have probably noted that we're using the JIRA Plugin for this case, where we're hoping to update each ticket in JIRA once a build succeeds. This works great when the build succeeds at first, but when it fails it doesn't show changes on the next run through. That might provide some

Re: Need help on usage of Jenkins console data

Below is the error. I am just listing my directory in the shell. In post build section creating a groovy script. + ls -lrt total 0 -rw-r--r-- 1 jenkins jenkins 0 Jun 15 06:25 build.log.copy ERROR: Failed to evaluate groovy script.groovy.lang.MissingPropertyException

What are the rules for Jenkins Pipeline to allocate workspaces, are ephemeral workspaces possible?

Hey folks, I'd like to understand how Jenkins Pipeline allocates workspaces - I'm alarmed that subsequent node {} elements in a Jenkinsfile appears to allocate the same workspace. It's causing problems with conflicting or missing files. My Jenkinsfile looks like this; stage "Testing"

Re: Split Pipeline script into multiple files -- run it without unnecessary nodes

Hi, thanks .. this seems to look like this will solve my problem... Will report back if it doesn't Am Mittwoch, 15. Juni 2016 15:00:36 UTC+2 schrieb Sverre Moe: > > Take a look at Pipeline Global Library > https://github.com/jenkinsci/workflow-cps-global-lib-plugin > I started with the same

Re: Split Pipeline script into multiple files -- run it without unnecessary nodes

Take a look at Pipeline Global Library https://github.com/jenkinsci/workflow-cps-global-lib-plugin I started with the same problem as you now have and solved it by using global pipeline scripts. These global script are stored in Jenkins git repository workflowLibs.git and can be accessed within

Re: structs plugin missing from https://updates.jenkins-ci.org/current/latest/ ?

Thanks! On Wed, Jun 15, 2016 at 6:14 AM Daniel Beck wrote: > > > On 15.06.2016, at 13:31, Mark Waite wrote: > > > > The structs plugin (structs.hpi) seems to be missing from the > current/latest directory at

Re: structs plugin missing from https://updates.jenkins-ci.org/current/latest/ ?

> On 15.06.2016, at 13:31, Mark Waite wrote: > > The structs plugin (structs.hpi) seems to be missing from the current/latest > directory at https://updates.jenkins-ci.org/current/latest/ . > > It is still available in https://updates.jenkins-ci.org/1.651/latest/ >

Setting PTC (MKS) Integrity environment variables through Jenkins configuration

Hello Everyone, I am new to Jenkins & don't really know much about it, have one doubt. Does Jenkins works sequentially as per the configuration ? Might be you wouldn't get any clear idea about doubt, So here we go with specific issue of mine : So I have attached a snapshot of my job

structs plugin missing from https://updates.jenkins-ci.org/current/latest/ ?

The structs plugin (structs.hpi) seems to be missing from the current/latest directory at https://updates.jenkins-ci.org/current/latest/ . It is still available in https://updates.jenkins-ci.org/1.651/latest/ It is still available in https://updates.jenkins-ci.org/stable/latest/ Is the

RE: Need help on usage of Jenkins console data

And the error was?? From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of AJITH K.R Sent: Wednesday, June 15, 2016 6:17 AM To: Jenkins Users Subject: Re: Need help on usage of Jenkins console data Thanks for the suggestion. I am completely new to groovy

Re: Jenkins shows no changes between a failed build (with changes) and the successful build that follows

On Tuesday, June 14, 2016 at 3:16:23 PM UTC-6, John O'Brien wrote: > > I had a user of our Jenkins system pose the following problem to me: > > > -- > > 1. A new build is started with changes. > 2. Note the changes are documented in the build description on Jenkins. > 3. Build fails in this

Re: Need help on usage of Jenkins console data

Thanks for the suggestion. I am completely new to groovy and I tried executing the script in post groovy step but it failed in step build.getLog() :-(. On Tuesday, June 14, 2016 at 5:46:45 PM UTC+5:30, rginga wrote: > > Ajith, I’m sure you can use a Post-build “Groovy Post-Build” to read the >

Re: Need help on usage of Jenkins console data

Thanks Nux for the suggestion. I have few more concerns. I use an enterprise version of Jenkins and I run the project in a linux slave. Is there any way i can get the path of the log. Using some $ commands as such. Please help me with this. Thanks, Ajith On Tuesday, June 14, 2016 at 10:36:06

Re: Windows Slave : Undocumented DCOM Issue : "JIException: Service Already Running" after reboot.

Some of this was caused by me accidentally having two Jenkins computers pointing at the same VM. But even once that was fixed it still happened from time to time after a reboot. So I worked around this by installing a scheduled task to run at bootup to disable the Jenkins slave. Then the

Re: Windows Slave - Connection reset when "scheduled slave overwrite" happens.

Just to close the loop here - it was my own mistake. In all my experimentation I had accidentally added to Jenkins computers that were speaking to the same VM so they were stepping on each others toes. Apologies for the wasted electrons and time. Cheers, Fred. On Monday, June 6, 2016 at