Re: [workflow-plugin] Using Closures in workflow scripts not allowed?

Hello, I found my problem. I was using a try-catch in my real production code, so the error was catched by my code, and not the sandbox, and I could not approve the exception. Now I made a little test to post here, and there I don't have the try-catch, which makes the script security catch the

[workflow-plugin] "Running Steps" shown twice

Hi, I have the same behavior like mentioned here https://issues.jenkins-ci.org/browse/JENKINS-26193 It's a job with 4 parallel steps. I have no idea what is causing this..

Parameterized Trigger Plugin - parameters for postjob is possible?

Hi All, I would have a question, maybe its quite trivial just I'm a bit stupid to find the solution. I am using "Parameterized Trigger Plugin". I defined more jobs under Build triggers, and could define parameters for them also. I can set a field called "Projects to build once, after all downs

Groovy Postbuild Plugin: Access Jenkins and not Hudson instance

The Groovy Postbuild plugin exposes some predefined variables like. - hudson - the current Hudson instance (javadoc ). I have checked the Javadoc and it looks like much of hudson instance is deprecated. *getInstance

Re: Groovy Postbuild Plugin: Access Jenkins and not Hudson instance

It's the same instance. On 04.03.2015, at 14:02, Sverre Moe wrote: > The Groovy Postbuild plugin exposes some predefined variables like. > • hudson - the current Hudson instance (javadoc). > > I have checked the Javadoc and it looks like much of hudson instance is > deprecated. > > getI

Want Build number and Build Status of other jobs

Hi, I am using Jeninks1.6 version. I have to mail Build Number, Build Status and version details of other jobs from other from my project in jenkins. i.e I want to access other jobs build number and version details in my project. I tried with *copy artifact Plugin* but it doesn't give me proper

How to run 3d party jars using jenkins build

Hi All Experts, I've below scenario as 1- I've created one maven project build 2- When ru via command prompt locally using mvn test all work well as included 3 party jars manually to .m2 . 3- Now when try to run via jenkins build it shows following error Could not find artifact custom-core-api

Re: Groovy Postbuild Plugin: Access Jenkins and not Hudson instance

Its a little confusing reading the API. What to use between jenkins.model or hudson.model The link points to hudson.model.Hudson, not jenkins.model.Jenkins http://javadoc.jenkins-ci.org/?hudson/model/Hudson.html Though I do see that Hudson extends Jenkins. onsdag 4. mars 2015 14.03.51 UTC+1 skre

Re: FATAL: org.apache.maven.wagon.providers.http.HttpWagon (initialization failure)

Hi, We are having the same problem in the following environment: Jenkins: 1.597 Maven: 3.2.5 and 3.2.3 JDK: 1.7 update 71 OS: Windows Server 2012 R2 Does anyone know the solution for this problem? Thank You! 2014. június 30., hétfő 6:49:02 UTC+2 időpontban Chris Graham a következőt írta:

RE: Want Build number and Build Status of other jobs

I can think of 2 options: If you use Build Flow or Work Flow jobs to run your other jobs, the “build” method returns an object you can use to get that information. You would then need to write that information to a file. Then, as a post build step, use the InjectEnv plugin to setup those values

need help with commit hooks and build order

I'm getting started with Jenkins and am running into one issue... I have my GitLab setup with a hook that kicks off my Jenkins job(s)... The problem is I several Jenkins jobs 1. Deploy project 2. Run unit tests on project 3. Run integration tests And my code / tests are in the same

Re: Groovy Postbuild Plugin: Access Jenkins and not Hudson instance

On 04.03.2015, at 14:12, Sverre Moe wrote: > Its a little confusing reading the API. What to use between jenkins.model or > hudson.model Jenkins used to be called Hudson until early 2011. Renaming packages breaks plugins relying on old names, so in general, any class predating 2011 will be in

Re: Warning: Problems with Jenkins 1.600 when env-inject is installed

I just rolled out 1.601 on two machines. It appears that the matrix project plugin version 1.4.1 is back. On one machine I attempted to both unpin and roll back the plugin version to 1.3. After a restart the plugin version remains at 1.4.1. I now no longer have the option of downgrading the plu

Re: Warning: Problems with Jenkins 1.600 when env-inject is installed

1.4.1 is bundled with Jenkins 1.600+. Are you experiencing any problems? Because it's only incompatible with earlier Jenkins versions. On 04.03.2015, at 17:09, Mark Eggers wrote: > I just rolled out 1.601 on two machines. It appears that the matrix project > plugin version 1.4.1 is back. On on

Jenkins 1.600 generates [FATAL] Non-resolvable parent POM: Could not find artifact (external to project) while parsing POMs

I have an organization POM file with all the settings necessary between projects. My multi module project is extending it and maven builds fine from CLI but when I run it through Jenkins I receive the following error: Parsing POMs ERROR: Failed to parse POMsorg.apache.maven.project.ProjectBuild

Re: Warning: Problems with Jenkins 1.600 when env-inject is installed

Not at this time. I'll wait to see when jobs are triggered by an SCM checkin. A quick check with a deploy job which uses BUILD_ID showed no issues. I just read the notice on the matrix project plugin page to not install that version. With the patch that addressed JENKINS-27188

Re: Jenkins 1.600 generates [FATAL] Non-resolvable parent POM: Could not find artifact (external to project) while parsing POMs

Try Jenkins 1.601 beforehand. 1.600 has been reported to have blocking issues. Not sure that one could be related though Le 4 mars 2015 17:26, "Paul Bors" a écrit : > I have an organization POM file with all the settings necessary between > projects. > > My multi module project is extending it an

Re: How to run 3d party jars using jenkins build

Did you try using a freestyle job or a maven one? Le 4 mars 2015 14:09, "kashu4055" a écrit : > Hi All Experts, > > I've below scenario as > > 1- I've created one maven project build > 2- When ru via command prompt locally using mvn test all work well as > included 3 party jars manually to .m2 .

[warnings-plugin] Not getting "warning: unused variable"

Hello, I've just installed the nice warnings plugin for an avr-gcc project, and configured it to scan the source as well as the console for warnings. I've put an unused variable on purpose and in the console I have: lambda.c: In function ‘display’: lambda.c:59:6: warning: unused variable ‘unus

Re: Jenkins 1.600 generates [FATAL] Non-resolvable parent POM: Could not find artifact (external to project) while parsing POMs

How do I manually upgrade to 1.601? I would beed at least the war. And why would they still allow an automatic upgrade to 1.600 if it's known to have issues? On Mar 4, 2015 11:52 AM, "Baptiste Mathus" wrote: > Try Jenkins 1.601 beforehand. 1.600 has been reported to have blocking > issues. Not

Re: Git Plugin Triggering Build Inaccurately

Hello All, This one is a follow-up for builds getting triggered for the changes not specified in "Include regions". We also added "force polling using workspace" option, but no luck. We ran into Jenkins Git plugin merge issue, and wanted to know if this can be addressed, and here is our scenar

Re: need help with commit hooks and build order

On Wed, Mar 04, 2015 at 07:44:05AM -0800, Jim Priest wrote: > I'm getting started with Jenkins and am running into one issue... > > I have my GitLab setup with a hook that kicks off my Jenkins job(s)... > > The problem is I several Jenkins jobs > >1. Deploy project >2. Run unit tests o

Git Client Plugin Include Region triggered Incorrect jobs

Hello All, This one is a follow-up for builds getting triggered for the changes not specified in "Include regions". We also added "force polling using workspace" option, but no luck. I posted the details in the below URL as well. Not sure if it's tracked. Apologize in advance for spamming: htt

Re: Jenkins 1.600 generates [FATAL] Non-resolvable parent POM: Could not find artifact (external to project) while parsing POMs

I didn't realize that 1.601 was released yesterday. Even after updating to 1.601 I'm still receiving the same error: Parsing POMs ERROR: Failed to parse POMs org.apache.maven.project.ProjectBuildingException

RE: Build Flow Plugin with Node Label Parameter Plugin

Found this as an explanation why you are getting builds on the same node: Scheduling strategy Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the fo

Re: Jenkins 1.600 generates [FATAL] Non-resolvable parent POM: Could not find artifact (external to project) while parsing POMs

Okay I figured out what the problem was. As it turns out during the upgrade I lost the contents of: \tools\hudson.tasks.Maven_MavenInstallation\Maven_3.x.x\conf\settings.xml Thus the embedded maven couldn't connect to our Nexus repositories and resolve the parent POM. The error was misleading a

YUM cacerts and Jenkins Upgrade - Now Git Connection Error - returned status code 128

One of our admins performed a YUM update on our AWS Linux Jenkins serve. CA Certs were updated as well as Jenkins. Now existing Jobs are failing and when we try to configure jobs with existing GitHub creds, we get the following errors in Jenkins: Failed to connect to repository : Command "g

RE: YUM cacerts and Jenkins Upgrade - Now Git Connection Error - returned status code 128

> -Original Message- > From: Jimmy Ray > Sent: Wednesday, March 04, 2015 16:57 > > One of our admins performed a YUM update on our AWS Linux > Jenkins serve. CA Certs were updated as well as Jenkins. There is a direcotry for you to put "your" cacerts, and then when yum updates the ro