Re: Pipeline problem after upgrading

2017-02-03 Thread Guy Knights
I just found this jira ticket: https://issues.jenkins-ci.org/browse/JENKINS-41339. Using the PATH+EXTENSION=/extension syntax in my System config -> Environment Variables fixed the problem for me. On Thu, Feb 2, 2017 at 4:27 PM, Guy Knights wrote: > I upgraded some of my pipeline plugins (there

Re: Pipeline problem after upgrading

2017-02-02 Thread Sam K
Yeah, we need to see the code to tell what's wrong with the syntax. Which version were you before the upgrade? And is it now at the latest as of this writing? On Thursday, February 2, 2017 at 4:27:42 PM UTC-8, Guy Knights wrote: > > I upgraded some of my pipeline plugins (there were some gro

Pipeline problem after upgrading

2017-02-02 Thread Guy Knights
I upgraded some of my pipeline plugins (there were some groovy module upgrades I believe, unfortunately I don't have a list of what was upgraded) and suddenly my build pipelines no longer work and are throwing the following error: Running on master in /var/jenkins_home/jobs/Project1/jobs/API - Dep