IDE for groovy

2014-06-29 Thread Pankaj Gupta
Hi, How can i use IDE for example: eclipse to write groovy for jenkins. I tried to run groovy but i do not have access to this object: Hudson.instance.items. I see this instance is available in groovy console/scriptler within jenkins jvm, i understand this but is there a way for us to create that

Re: Cobertura Publishing Abort - Linking Error

2014-06-29 Thread Ulli Hafner
Any reason why you are using WAS? Class loading errors typically occur if the container provides some incompatible jar versions. Jenkins will run without any class loading issues with the embedded Jetty container. Am 30.06.2014 um 07:19 schrieb Chris Graham : > Hi All. > > Running Jenkins 1.56

[no subject]

2014-06-29 Thread Panikera Raj
Hi All, I am not able to find the option under Manage Jenkins\Configure System\SVN category as: Update default Subversion credentials cache after successful authentication. What could be the issue. how to resolve such type of issue Pls let me know. Regards, Panikera -- You received this messag

Re: Problem with Clearcase plugin running many builds in parallel

2014-06-29 Thread Sascha Herrmann
Builds run fine now. Seems that endview takes some time to finish before the next command can be called. Would it be possible to get a delay like that into the official plugin? Maybe configurable with a system property? Sascha Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann:

Cobertura Publishing Abort - Linking Error

2014-06-29 Thread Chris Graham
Hi All. Running Jenkins 1.566 on WAS 8.5.5.2 using the IBM 1.7 JDK on RHEL 5.10. I'm seeing this error after having succesfully built a job that uses the M2 job type. It's occurring after the archiving and when the Cobertura publisher runs. channel stopped [Cobertura] Publishing Cobertura cove

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

2014-06-29 Thread Chris Graham
Hi All. I've installed Jenkins 1.566 into WAS 8.5.5.2, using the IBM 1.6 JDK on RHEL 5.10. I have some M2 Job types. When Jenkins does it's internal parsing of the poms, it dies with this error: FATAL: org.apache.maven.wagon.providers.http.HttpWagon (initialization failure)java.lang.NoClassD

parameterized remote trigger plugin behavior

2014-06-29 Thread Simon Haegler
hi jenkins users i fail to understand the behavior of the "parameterized remote trigger plugin". the "wait to trigger.." and "block" options are enabled. here is what i get: Connection to remote server failed, waiting for to retry - 30 seconds until next attempt. > Retry attempt #1 out of 5 > C