Parallel Deployment+ Tomcat 7.x + Grails 2.2.x
Hi I'll be concise, sorry. I know there was a similar issue bug n.13855, but it seems not to be fixed in my environment. Jenkins 1.506 Tomcat 7.0.35 Grails 2.2.1 If I deploy a normal war everything works fine, if I deploy a with a parallel deployment (name##version_number.war) it fails, even if then the file itself is correctly deployed. It seems the system doesn't recognise the sub version. At the bottom you see /Lumen//0718, I don't know if it's the double slash. Thanks for any good advice AdoTedo Here the log: Deploying /home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war to container Tomcat 7.x Remote [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] is not deployed. Doing a fresh deployment. Deploying [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:111) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:187) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Failed to deploy application at context path /Lumen//0718 -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Build flow plugin does not visualize the flow correctly
Hi,
I have an issue with bulid flow plugin. The defined flow is executed
correctly (visible in Console Output) but the flow graph is being cut at
some point of time and to further jobs from chain are ploted. the flow is
the following:
build(JOB-1)
parallel (
{
ignore(FAILURE) { build(JOB-2-1) }
ignore(FAILURE) { build(JOB-2-2) }
ignore(FAILURE) { build(JOB-2-3) }
},
{
ignore(FAILURE) { build(JOB-3-1) }
ignore(FAILURE) { build(JOB-3-2) }
},
{
ignore(FAILURE) { build(JOB-4-1) }
ignore(FAILURE) { build(JOB-4-2) }
ignore(FAILURE) { build(JOB-4-3) }
ignore(FAILURE) { build(JOB-4-4) }
}
)
build(JOB-5)
But on diagram I can see only the following:
JOB-2-1 - JOB-2-2 - JOB-2-3 - JOB-5
JOB-1 - JOB-3-1
JOB-4-1
Somehow further jobs from chain 3 and 4 are not plotted.
Any idea that is wrong here?
Thanks for help
Regards
Pawel W.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Build flow plugin does not visualize the flow correctly
flow visualization is still early stage, and probably need some love to
address complex graphs.
We are extracting it into a more general purpose plugin (build graph view)
so it can both handle flows and classic jenkins downstream chains
2013/3/21 Pawel Wrobel pawel.wro...@nsn.com
Hi,
I have an issue with bulid flow plugin. The defined flow is executed
correctly (visible in Console Output) but the flow graph is being cut at
some point of time and to further jobs from chain are ploted. the flow is
the following:
build(JOB-1)
parallel (
{
ignore(FAILURE) { build(JOB-2-1) }
ignore(FAILURE) { build(JOB-2-2) }
ignore(FAILURE) { build(JOB-2-3) }
},
{
ignore(FAILURE) { build(JOB-3-1) }
ignore(FAILURE) { build(JOB-3-2) }
},
{
ignore(FAILURE) { build(JOB-4-1) }
ignore(FAILURE) { build(JOB-4-2) }
ignore(FAILURE) { build(JOB-4-3) }
ignore(FAILURE) { build(JOB-4-4) }
}
)
build(JOB-5)
But on diagram I can see only the following:
JOB-2-1 - JOB-2-2 - JOB-2-3 - JOB-5
JOB-1 - JOB-3-1
JOB-4-1
Somehow further jobs from chain 3 and 4 are not plotted.
Any idea that is wrong here?
Thanks for help
Regards
Pawel W.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: Build flow plugin does not visualize the flow correctly
Hi,
I guess this one is still under work right
(https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin)?
Any expectations when it may be ready to use?
---
Serdecznie pozdrawiam/ With kind regards/ Mit freundlichen Gruessen
Paweł Wróbel
Nokia Siemens Networks Sp. z o. o. / *
MSP BSS RD Unified Tooling and IPD
IP-Dispatcher Development
mobile: +48 728 455 306
e-mail: pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of ext nicolas de loof
Sent: Thursday, March 21, 2013 9:22 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin does not visualize the flow correctly
flow visualization is still early stage, and probably need some love to address
complex graphs.
We are extracting it into a more general purpose plugin (build graph view) so
it can both handle flows and classic jenkins downstream chains
2013/3/21 Pawel Wrobel pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
Hi,
I have an issue with bulid flow plugin. The defined flow is executed correctly
(visible in Console Output) but the flow graph is being cut at some point of
time and to further jobs from chain are ploted. the flow is the following:
build(JOB-1)
parallel (
{
ignore(FAILURE) { build(JOB-2-1) }
ignore(FAILURE) { build(JOB-2-2) }
ignore(FAILURE) { build(JOB-2-3) }
},
{
ignore(FAILURE) { build(JOB-3-1) }
ignore(FAILURE) { build(JOB-3-2) }
},
{
ignore(FAILURE) { build(JOB-4-1) }
ignore(FAILURE) { build(JOB-4-2) }
ignore(FAILURE) { build(JOB-4-3) }
ignore(FAILURE) { build(JOB-4-4) }
}
)
build(JOB-5)
But on diagram I can see only the following:
JOB-2-1 - JOB-2-2 - JOB-2-3 - JOB-5
JOB-1 - JOB-3-1
JOB-4-1
Somehow further jobs from chain 3 and 4 are not plotted.
Any idea that is wrong here?
Thanks for help
Regards
Pawel W.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: Build flow plugin does not visualize the flow correctly
There is no such thing as a soft without bugs;)
Means: I would have to wait for a couple of weeks for a release
Thanks☺
---
Serdecznie pozdrawiam/ With kind regards/ Mit freundlichen Gruessen
Paweł Wróbel
Nokia Siemens Networks Sp. z o. o. / •
MSP BSS RD Unified Tooling and IPD
IP-Dispatcher Development
mobile: +48 728 455 306
e-mail: pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of ext nicolas de loof
Sent: Thursday, March 21, 2013 9:35 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin does not visualize the flow correctly
2013/3/21 Wrobel, Pawel (NSN - PL/Wroclaw)
pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
Hi,
I guess this one is still under work right
(https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin)?
Any expectations when it may be ready to use?
mostly depends what you consider ready to use.
if you're asking for a release we could probably have one in few weeks (I'm
going to Devoxx France so won't have much spare time next week)
if you're asking for a bug-free version, we probably never will have one :)
---
Serdecznie pozdrawiam/ With kind regards/ Mit freundlichen Gruessen
Paweł Wróbel
Nokia Siemens Networks Sp. z o. o. / •
MSP BSS RD Unified Tooling and IPD
IP-Dispatcher Development
mobile: +48 728 455 306tel:%2B48%20728%20455%20306
e-mail: pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com]
On Behalf Of ext nicolas de loof
Sent: Thursday, March 21, 2013 9:22 AM
To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin does not visualize the flow correctly
flow visualization is still early stage, and probably need some love to address
complex graphs.
We are extracting it into a more general purpose plugin (build graph view) so
it can both handle flows and classic jenkins downstream chains
2013/3/21 Pawel Wrobel pawel.wro...@nsn.commailto:pawel.wro...@nsn.com
Hi,
I have an issue with bulid flow plugin. The defined flow is executed correctly
(visible in Console Output) but the flow graph is being cut at some point of
time and to further jobs from chain are ploted. the flow is the following:
build(JOB-1)
parallel (
{
ignore(FAILURE) { build(JOB-2-1) }
ignore(FAILURE) { build(JOB-2-2) }
ignore(FAILURE) { build(JOB-2-3) }
},
{
ignore(FAILURE) { build(JOB-3-1) }
ignore(FAILURE) { build(JOB-3-2) }
},
{
ignore(FAILURE) { build(JOB-4-1) }
ignore(FAILURE) { build(JOB-4-2) }
ignore(FAILURE) { build(JOB-4-3) }
ignore(FAILURE) { build(JOB-4-4) }
}
)
build(JOB-5)
But on diagram I can see only the following:
JOB-2-1 - JOB-2-2 - JOB-2-3 - JOB-5
JOB-1 - JOB-3-1
JOB-4-1
Somehow further jobs from chain 3 and 4 are not plotted.
Any idea that is wrong here?
Thanks for help
Regards
Pawel W.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: How to connect to a Linux slave?
Hi What do you mean that an Ubuntu slave uses Windows authentication? As I said before, you need to try logging into the slave directly via ssh. When that works, try it with Jenkins. Ok, please ignore my 'Windows authentication' comment. Yes, I can try SSH, but my understanding is that if I specify a username/password in the 'Advanced' settings it shouldn't be necessary to use SSH. I don't understand why the username/password method is not working on the Ubuntu slave. BR David -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- us...@googlegroups.com] On Behalf Of Jonathan Rogers Sent: 20 March 2013 17:24 To: jenkinsci-users@googlegroups.com Subject: Re: How to connect to a Linux slave? David Aldrich wrote: Hi Les, Yes I have and I have entered the correct username and password. But I still get: [03/20/13 16:56:01] [SSH] Opening SSH connection to tmds404:22. java.io.IOException: There was a problem while connecting to tmds404:22 at com.trilead.ssh2.Connection.connect(Connection.java:793) at com.trilead.ssh2.Connection.connect(Connection.java:565) The only differences between this slave and the others (apart from it running Ubuntu) is that it uses Windows authentication not Linux authentication. What do you mean that an Ubuntu slave uses Windows authentication? As I said before, you need to try logging into the slave directly via ssh. When that works, try it with Jenkins. -- Jonathan Rogers -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Click https://www.mailcontrol.com/sr/KOTwI1zAHvnGX2PQPOmvUrwgXREt4LZXC gi9HnTlFn2dqHDSniPhooeUUzO+ssbqXeCWFTId+Sn5pl0FDW8fzw== to report this email as spam. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Build of first commit on git branch does not show changes
git-plugin maintain the last build per branch, but dones not try to discover when a branch was created compared to previous builds. Not trivial to implement 2013/3/21 Brian Jones caneri...@gmail.com Is it possible to get Jenkins to detect and report Changes for the first commit on a new branch/build? I'm setting up feature based development in git: * Feature branches are named after an issue ID (e.g., JIRA issue ID) * Feature branches based on git master branch * Commits to feature branch trigger Jenkins build for that feature I've noticed that Jenkins only reports the git commit ID but does not report that anything changed for the first commit to any feature branch. This means that I must post at least two commits to any feature branch in order for Jenkins to see the issue ID and note changes. The first commit looks like this: https://lh6.googleusercontent.com/-0WARGRr7E-M/UUp5NgD15aI/Kls/B3FxF1ZMz38/s1600/JENKINS1-2013-03-20+19_23_38-branch_test7+%232+%5BJenkins%5D.png The second commit looks like this: https://lh3.googleusercontent.com/-R6pob8lnZMA/UUp5c9Mpo-I/Kl0/FovmZnxzENk/s1600/JENKINS2-2013-03-20+19_31_29-branch_test7+%2312+%5BJenkins%5D.png Brian -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Getting exception when trying to build maven project by perforce plugin
This appears to be JENKINS-16256 https://issues.jenkins-ci.org/browse/JENKINS-16256, which is a duplicate ofJENKINS-15642. https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric https://issues.jenkins-ci.org/browse/JENKINS-15642 On 3/20/2013 6:01 PM, devanand wrote: Yes i had corrected earlier but some how Jenkins was not able to delete this information from it's cache, Even i restarted many times... Eventually i needed to delete that proejct and resetup again.. Then only it corrected the value with -XX:MaxPermSize=128m. After correcting this i am not getting execption below.. Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #10 ASC: lo=10,hi=0,size=10,size2=10 cause : Assertion error: failing to load #10 ASC: lo=10,hi=0,size=10,size2=10 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #10 ASC: lo=10,hi=0,size=10,size2=10 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Maven jenkins build is throwing exception.
This isJENKINS-15642. https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric On 3/20/2013 8:34 PM, devanand wrote: Hi, I am getting following exception even though i can see my build is successfull. I can see on local box this has artifact available but still i can see this error whenever i run my jenkins maven build job Please check the attachment of configuration which i am doingn for this project... Please help me to find out the problem I think this is Jenkins Plugin problem or correct me if any other configuration i need to do here INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.602s [INFO] Finished at: Wed Mar 20 17:28:49 PDT 2013 [INFO] Final Memory: 10M/156M [INFO] [JENKINS] Archiving disabled Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 cause : Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractBuild.getNextBuild(AbstractBuild.java:244) at hudson.maven.MavenModuleSetBuild.getModuleBuilds(MavenModuleSetBuild.java:275) at hudson.maven.MavenModuleSetBuild.notifyModuleBuild(MavenModuleSetBuild.java:500) at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:506) at sun.reflect.GeneratedMethodAccessor532.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.model.Executor$1.call(Executor.java:543) at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23) at $Proxy45.end(Unknown Source) at sun.reflect.GeneratedMethodAccessor531.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at
Re: How to connect to a Linux slave?
On Thu, Mar 21, 2013 at 4:06 AM, David Aldrich david.aldr...@emea.nec.com wrote: Hi What do you mean that an Ubuntu slave uses Windows authentication? As I said before, you need to try logging into the slave directly via ssh. When that works, try it with Jenkins. Ok, please ignore my 'Windows authentication' comment. Yes, I can try SSH, but my understanding is that if I specify a username/password in the 'Advanced' settings it shouldn't be necessary to use SSH. I don't understand why the username/password method is not working on the Ubuntu slave. Well, if you would 'ssh -vv' from the jenkins server to the host that is refusing the connection, you might get very verbose messages telling you why. I doubt if anyone on the list is going to guess the answer for you. Normally passwords or keys should work. -- Les Mikesell lesmikes...@gmail.com -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins CVS checkout creates world writable files
I just started setting up jenkins 1.506 on CentOS 5.9 as described on https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions I've configured it to checkout from our CVS repo via pserver and CVSROOT=:pserver:jenkins@host:/repodir. However, when I look at the checked out tree in the workspace, files have permissions 666 or 777 (world writable, ugh!) and directories have permissions 755. I have already tried the following with no effect: * Added umask 002 early in /etc/init.d/jenkins and restarted jenkins * Added umask 002 to Build-Execute Shell (pointless because this is run after checkout; even without this, displaying the umask shows 002, which is proper, but for some reason not applied during CVS checkout) * Added CVSUMASK=002 to Configure System-Global Properties- Environment Variables and restarted jenkins Everything has proper permissions when checked out manually by developers, even without anyone using CVSUMASK. I'm stumped. Someone please hit me with the clue bat. Regards, Jens -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins CVS checkout creates world writable files
Which version of the cvs plugin are you using? Thanks Michael On 21 Mar 2013, at 13:43, Jens Schweikhardt use...@schweikhardt.net wrote: I just started setting up jenkins 1.506 on CentOS 5.9 as described on https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+RedHat+distributions I've configured it to checkout from our CVS repo via pserver and CVSROOT=:pserver:jenkins@host:/repodir. However, when I look at the checked out tree in the workspace, files have permissions 666 or 777 (world writable, ugh!) and directories have permissions 755. I have already tried the following with no effect: * Added umask 002 early in /etc/init.d/jenkins and restarted jenkins * Added umask 002 to Build-Execute Shell (pointless because this is run after checkout; even without this, displaying the umask shows 002, which is proper, but for some reason not applied during CVS checkout) * Added CVSUMASK=002 to Configure System-Global Properties- Environment Variables and restarted jenkins Everything has proper permissions when checked out manually by developers, even without anyone using CVSUMASK. I'm stumped. Someone please hit me with the clue bat. Regards, Jens -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: How to connect to a Linux slave?
Hi Les Thanks for your reply. That helped me realise that I had made a stupid mistake by misspelling the host name. It all works now. BR David -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- us...@googlegroups.com] On Behalf Of Les Mikesell Sent: 21 March 2013 12:35 To: jenkinsci-users@googlegroups.com Subject: Re: How to connect to a Linux slave? On Thu, Mar 21, 2013 at 4:06 AM, David Aldrich david.aldr...@emea.nec.com wrote: Hi What do you mean that an Ubuntu slave uses Windows authentication? As I said before, you need to try logging into the slave directly via ssh. When that works, try it with Jenkins. Ok, please ignore my 'Windows authentication' comment. Yes, I can try SSH, but my understanding is that if I specify a username/password in the 'Advanced' settings it shouldn't be necessary to use SSH. I don't understand why the username/password method is not working on the Ubuntu slave. Well, if you would 'ssh -vv' from the jenkins server to the host that is refusing the connection, you might get very verbose messages telling you why. I doubt if anyone on the list is going to guess the answer for you. Normally passwords or keys should work. -- Les Mikesell lesmikes...@gmail.com -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Click https://www.mailcontrol.com/sr/NIJ!sjcJzfPGX2PQPOmvUs3oG7lEfVxCFWu! 5q9VhFwHeGvkfhzuhDkoevdjI8!CAzNTk47hsmH1JTd!1uc+!w== to report this email as spam. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins CVS checkout creates world writable files
Michael et al., On Mar 21, 2:45 pm, Michael Clarke michael.m.cla...@gmail.com wrote: Which version of the cvs plugin are you using? 2.8 (upgraded from stock 1.6 as suggested by jenkins) Jens -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Parallel Deployment+ Tomcat 7.x + Grails 2.2.x
Hi guys, I'm me again. In my previous post I said that the deploy at the end works even with failure, but unfortunately it's not true. It has problems. If I deploy the war without ##version everything works fine, if I deploy it manually, compile, move the war and so on it works even it's in version format. The problem seems that jenkis doesn't like parallel deploy. Any clue? thanks a lot On Thursday, March 21, 2013 7:41:57 AM UTC+1, AdoTedo wrote: Hi I'll be concise, sorry. I know there was a similar issue bug n.13855, but it seems not to be fixed in my environment. Jenkins 1.506 Tomcat 7.0.35 Grails 2.2.1 If I deploy a normal war everything works fine, if I deploy a with a parallel deployment (name##version_number.war) it fails, even if then the file itself is correctly deployed. It seems the system doesn't recognise the sub version. At the bottom you see /Lumen//0718, I don't know if it's the double slash. Thanks for any good advice AdoTedo Here the log: Deploying /home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war to container Tomcat 7.x Remote [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] is not deployed. Doing a fresh deployment. Deploying [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/tomcat/.jenkins/jobs/Lumen-CI/workspace/target/Lumen##0718.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:111) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:187) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Failed to deploy application at context path /Lumen//0718 -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
GIT stopped working after upgrading the plugin to version 1.3.0
Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:418) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1026) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) at org.eclipse.jgit.util.HttpSupport.response(HttpSupport.java:167) at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:459) ... 19 more Caused by: sun.security.validator.ValidatorException: PKIX path building failed:
Re: GIT stopped working after upgrading the plugin to version 1.3.0
Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bruc...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:418) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1026) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373) at
Re: Build of first commit on git branch does not show changes
I think for this use case just showing the commits since the branch point would be an acceptable compromise. If the branch includes commits (from its parent branch) that have not been built in another job, I don't think there is any practical way the plugin could figure that out (or that doing so would even be relevant). - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Mar 21 2013 05:24:15 git-plugin maintain the last build per branch, but dones not try to discover when a branch was created compared to previous builds. Not trivial to implement 2013/3/21 Brian Jones caneri...@gmail.com Is it possible to get Jenkins to detect and report Changes for the first commit on a new branch/build? I'm setting up feature based development in git: * Feature branches are named after an issue ID (e.g., JIRA issue ID) * Feature branches based on git master branch * Commits to feature branch trigger Jenkins build for that feature I've noticed that Jenkins only reports the git commit ID but does not report that anything changed for the first commit to any feature branch. This means that I must post at least two commits to any feature branch in order for Jenkins to see the issue ID and note changes. The first commit looks like this: https://lh6.googleusercontent.com/-0WARGRr7E-M/UUp5NgD15aI/Kls/B3FxF1ZMz38/s1600/JENKINS1-2013-03-20+19_23_38-branch_test7+%232+%5BJenkins%5D.png The second commit looks like this: https://lh3.googleusercontent.com/-R6pob8lnZMA/UUp5c9Mpo-I/Kl0/FovmZnxzENk/s1600/JENKINS2-2013-03-20+19_31_29-branch_test7+%2312+%5BJenkins%5D.png Brian -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Environment variables from Jenkins TestLink Plug-in
Hi, Nobody have ideas . Or just the sample of tutorial of plug-in Le 06/03/2013 09:40, Marcellino Palerme a écrit : Hi I work on Jenkins 1.504 and Jenkins TestLink Plugin 3.1.8. When I try read the environment variables provides by plugin like TESTLINK_TESTCASE_ID or TESTLINK_BUILD_NAME, they are empty. Could you help me ? please -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- *Cordialement / Best regards* *Marcellino PALERME* *Technicien testeur / technician tester* http://www.jftl.org/ KEREVAL 4, rue Hélène Boucher Z.A. Bellevue 35235 Thorigné Fouillard Tel : +33 (0)2 23 20 36 64 *http://www.kereval.com * -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. inline: jftl.gif
Re: GIT stopped working after upgrading the plugin to version 1.3.0
as a temporary workaround run jenkins with org.jenkinsci.plugins.gitclient.Git.useCLI=true I'm disappointed with JGit, and probably will revert git-client to use git-cli by default, even this has some serious drawbacks, until JGit gets more mature. 2013/3/21 Peter Miklosko peter.b...@gmail.com Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bruc...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:418) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
That workaround doesn't work if you have slave nodes. The one that worked for me is detailed in the Jira: https://issues.jenkins-ci.org/browse/JENKINS-17204?focusedCommentId=175804#comment-175804 That works just great for me now. On Thu, Mar 21, 2013 at 8:40 AM, nicolas de loof nicolas.del...@gmail.comwrote: as a temporary workaround run jenkins with org.jenkinsci.plugins.gitclient.Git.useCLI=true I'm disappointed with JGit, and probably will revert git-client to use git-cli by default, even this has some serious drawbacks, until JGit gets more mature. 2013/3/21 Peter Miklosko peter.b...@gmail.com Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bruc...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
Thank you, I've added -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com javascript:wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:418) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
You have to configure slaves as well to use this option 2013/3/21 Jared Griffith jgriff...@picsauditing.com That workaround doesn't work if you have slave nodes. The one that worked for me is detailed in the Jira: https://issues.jenkins-ci.org/browse/JENKINS-17204?focusedCommentId=175804#comment-175804 That works just great for me now. On Thu, Mar 21, 2013 at 8:40 AM, nicolas de loof nicolas.del...@gmail.com wrote: as a temporary workaround run jenkins with org.jenkinsci.plugins.gitclient.Git.useCLI=true I'm disappointed with JGit, and probably will revert git-client to use git-cli by default, even this has some serious drawbacks, until JGit gets more mature. 2013/3/21 Peter Miklosko peter.b...@gmail.com Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bruc...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bruc...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/** workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/**workspace/Megapixel_04.07.00 - hudson.remoting.Channel@**61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e**109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/** megapixel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.**GitException: org.eclipse.jgit.api.errors.**TransportException: https://git.example.com/**megapixel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.**gitclient.JGitAPIImpl.fetch(** JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.**fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.**invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.**invoke(GitSCM.java:941) at hudson.FilePath$**FileCallableWrapper.call(**FilePath.java:2246) at hudson.remoting.UserRequest.**perform(UserRequest.java:118) at hudson.remoting.UserRequest.**perform(UserRequest.java:48) at hudson.remoting.Request$2.run(**Request.java:326) at hudson.remoting.**InterceptingExecutorService$1.**call(** InterceptingExecutorService.**java:72) at java.util.concurrent.**FutureTask$Sync.innerRun(** FutureTask.java:303) at java.util.concurrent.**FutureTask.run(FutureTask.**java:138) at java.util.concurrent.**ThreadPoolExecutor$Worker.** runTask(ThreadPoolExecutor.**java:886) at java.util.concurrent.**ThreadPoolExecutor$Worker.run(** ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.**java:619) Caused by: org.eclipse.jgit.api.errors.**TransportException: https://git.example.com/**megapixel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.**FetchCommand.call(**FetchCommand.java:137) at org.jenkinsci.plugins.**gitclient.JGitAPIImpl.fetch(** JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.**TransportException: https://git.example.com/**megapixel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.**TransportHttp.connect(** TransportHttp.java:496) at org.eclipse.jgit.transport.**TransportHttp.openFetch(** TransportHttp.java:305) at org.eclipse.jgit.transport.**FetchProcess.executeImp(** FetchProcess.java:136) at org.eclipse.jgit.transport.**FetchProcess.execute(** FetchProcess.java:122) at org.eclipse.jgit.transport.**Transport.fetch(Transport.**java:1104) at org.eclipse.jgit.api.**FetchCommand.call(**FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.**SSLHandshakeException: sun.security.validator.**ValidatorException: PKIX path building failed: sun.security.provider.**certpath.**SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.**Alerts.getSSLException(Alerts.** java:174) at com.sun.net.ssl.internal.ssl.**SSLSocketImpl.fatal(** SSLSocketImpl.java:1611) at com.sun.net.ssl.internal.ssl.**Handshaker.fatalSE(Handshaker.** java:187) at com.sun.net.ssl.internal.ssl.**Handshaker.fatalSE(Handshaker.** java:181) at com.sun.net.ssl.internal.ssl.**ClientHandshaker.**serverCertificate( **ClientHandshaker.java:1035)
Re: Maven jenkins build is throwing exception.
Hi Eric, When should i expect to be resolved this BUG ? or is there any work around to this problem ??? Thanks. On Thursday, March 21, 2013 5:28:58 AM UTC-7, Eric Pyle wrote: This is JENKINS-15642.https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric On 3/20/2013 8:34 PM, devanand wrote: Hi, I am getting following exception even though i can see my build is successfull. I can see on local box this has artifact available but still i can see this error whenever i run my jenkins maven build job Please check the attachment of configuration which i am doingn for this project... Please help me to find out the problem I think this is Jenkins Plugin problem or correct me if any other configuration i need to do here INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.602s [INFO] Finished at: Wed Mar 20 17:28:49 PDT 2013 [INFO] Final Memory: 10M/156M [INFO] [JENKINS] Archiving disabled Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 cause : Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractBuild.getNextBuild(AbstractBuild.java:244) at hudson.maven.MavenModuleSetBuild.getModuleBuilds(MavenModuleSetBuild.java:275) at hudson.maven.MavenModuleSetBuild.notifyModuleBuild(MavenModuleSetBuild.java:500) at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:506) at sun.reflect.GeneratedMethodAccessor532.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.model.Executor$1.call(Executor.java:543) at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23) at $Proxy45.end(Unknown Source) at sun.reflect.GeneratedMethodAccessor531.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at
Re: Maven jenkins build is throwing exception.
Sorry, I don't know when it may be fixed. I am not involved in working on it. As for a workaround, the bug reporter says if the build is manually started, it succeeds - not sure if you've tried that. To still have builds triggered automatically, you could set up a post-commit hook in your source control system to trigger builds when changes are committed. Details depend on which SCM you use. For Git, see http://blog.cloudbees.com/2011/11/polling-must-die-triggering-jenkins.html. Regards, Eric On 3/21/2013 12:29 PM, devanand wrote: Hi Eric, When should i expect to be resolved this BUG ? or is there any work around to this problem ??? Thanks. On Thursday, March 21, 2013 5:28:58 AM UTC-7, Eric Pyle wrote: This isJENKINS-15642. https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric On 3/20/2013 8:34 PM, devanand wrote: Hi, I am getting following exception even though i can see my build is successfull. I can see on local box this has artifact available but still i can see this error whenever i run my jenkins maven build job Please check the attachment of configuration which i am doingn for this project... Please help me to find out the problem I think this is Jenkins Plugin problem or correct me if any other configuration i need to do here INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.602s [INFO] Finished at: Wed Mar 20 17:28:49 PDT 2013 [INFO] Final Memory: 10M/156M [INFO] [JENKINS] Archiving disabled Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 cause : Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractBuild.getNextBuild(AbstractBuild.java:244) at hudson.maven.MavenModuleSetBuild.getModuleBuilds(MavenModuleSetBuild.java:275) at hudson.maven.MavenModuleSetBuild.notifyModuleBuild(MavenModuleSetBuild.java:500) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
right, there is no LTS concept for plugins 2013/3/21 Aldo Brucale bruc...@gmail.com So also the LTS version of Jenkins pulls the latest version of the plugins. I thought it was safe to keep them updated... On Thursday, 21 March 2013 17:03:29 UTC+1, Nicolas De loof wrote: There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bru...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.**gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/** workspa**ce/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/**workspa**ce/Megapixel_04.07.00 - hudson.remoting.Channel@**61df09**2e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.**GitExceptio**n: org.eclipse.jgit.api.errors.**Tr* *ansportException: https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp **l.java:212) at hudson.plugins.git.GitAPI.**fetc**h(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:941) at hudson.FilePath$**FileCallableWr**apper.call(**FilePath.java:2246) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:118) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.**InterceptingEx**ecutorService$1.**call(** Intercept**ingExecutorService.**java:72) at java.util.concurrent.**FutureTas**k$Sync.innerRun(**FutureTask.** java:303) at java.util.concurrent.**FutureTas**k.run(FutureTask.**java:138) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.**runTask(** ThreadPoolExecutor.**java:886) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.run(**ThreadPoo **lExecutor.java:908) at java.lang.Thread.run(Thread.**ja**va:619) Caused by: org.eclipse.jgit.api.errors.**Tr**ansportException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 137) at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp* *l.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.**Transp**ortException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.**Tra**nsportHttp.connect(**TransportHt **tp.java:496) at org.eclipse.jgit.transport.**Tra**nsportHttp.openFetch(**Transport* *Http.java:305) at org.eclipse.jgit.transport.**Fet**chProcess.executeImp(**FetchProc **ess.java:136) at org.eclipse.jgit.transport.**Fet**chProcess.execute(**FetchProcess* *.java:122) at org.eclipse.jgit.transport.**Tra**nsport.fetch(Transport.**java:** 1104) at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 128) ... 14 more Caused by: javax.net.ssl.**SSLHandshakeExce**ption: sun.security.validator.**Validat**orException: PKIX path building failed: sun.security.provider.**certpath**.**SunCertPathBuilderException: unable to find valid certification path to requested target at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
I've often wished there was a way to do this though. On Thu, Mar 21, 2013 at 10:22 AM, nicolas de loof nicolas.del...@gmail.comwrote: right, there is no LTS concept for plugins 2013/3/21 Aldo Brucale bruc...@gmail.com So also the LTS version of Jenkins pulls the latest version of the plugins. I thought it was safe to keep them updated... On Thursday, 21 March 2013 17:03:29 UTC+1, Nicolas De loof wrote: There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bru...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.**gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/* *workspa**ce/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/**workspa**ce/Megapixel_04.07.00 - hudson.remoting.Channel@**61df09**2e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.**GitExceptio**n: org.eclipse.jgit.api.errors.**Tr **ansportException: https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(** JGitAPIImp**l.java:212) at hudson.plugins.git.GitAPI.**fetc**h(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:941) at hudson.FilePath$**FileCallableWr**apper.call(** FilePath.java:2246) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:118) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.**InterceptingEx**ecutorService$1.**call(** Intercept**ingExecutorService.**java:72) at java.util.concurrent.**FutureTas**k$Sync.innerRun(**FutureTask.** java:303) at java.util.concurrent.**FutureTas**k.run(FutureTask.**java:138) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.**runTask(** ThreadPoolExecutor.**java:886) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.run(** ThreadPoo**lExecutor.java:908) at java.lang.Thread.run(Thread.**ja**va:619) Caused by: org.eclipse.jgit.api.errors.**Tr**ansportException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 137) at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp **l.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.**Transp**ortException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.**Tra**nsportHttp.connect(** TransportHt**tp.java:496) at org.eclipse.jgit.transport.**Tra**nsportHttp.openFetch(**Transport **Http.java:305) at org.eclipse.jgit.transport.**Fet**chProcess.executeImp(** FetchProc**ess.java:136) at org.eclipse.jgit.transport.**Fet**chProcess.execute(**FetchProcess **.java:122) at org.eclipse.jgit.transport.**Tra**nsport.fetch(Transport.**java:* *1104) at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 128) ... 14 more Caused by: javax.net.ssl.**SSLHandshakeExce**ption: sun.security.validator.**Validat**orException: PKIX path building failed:
Re: GIT stopped working after upgrading the plugin to version 1.3.0
Being a relative newbie here I'm a bit hesitant to throw this out... but with the massive growth in the Jenkins community over the last year or more, maybe it's time to consider having a 'stable' and 'unstable' plugin repositories as well. Developers need ways to test out new things (like has been done with the Git plugins), but users also need ways to stick with plugins that they are comfortable with. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Mar 21 2013 13:23:29 right, there is no LTS concept for plugins 2013/3/21 Aldo Brucale bruc...@gmail.com So also the LTS version of Jenkins pulls the latest version of the plugins. I thought it was safe to keep them updated... On Thursday, 21 March 2013 17:03:29 UTC+1, Nicolas De loof wrote: There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bru...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.**gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/** workspa**ce/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/**workspa**ce/Megapixel_04.07.00 - hudson.remoting.Channel@**61df09**2e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.**GitExceptio**n: org.eclipse.jgit.api.errors.**Tr* *ansportException: https://git.example.com/**megapi** xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp **l.java:212) at hudson.plugins.git.GitAPI.**fetc**h(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:941) at hudson.FilePath$**FileCallableWr**apper.call(**FilePath.java:2246) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:118) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.**InterceptingEx**ecutorService$1.**call(** Intercept**ingExecutorService.**java:72) at java.util.concurrent.**FutureTas**k$Sync.innerRun(**FutureTask.** java:303) at java.util.concurrent.**FutureTas**k.run(FutureTask.**java:138) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.**runTask(** ThreadPoolExecutor.**java:886) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.run(**ThreadPoo **lExecutor.java:908) at java.lang.Thread.run(Thread.**ja**va:619) Caused by: org.eclipse.jgit.api.errors.**Tr**ansportException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 137) at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp* *l.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.**Transp**ortException: https://git.example.com/**megapi**xel/my_build_tools.githttps://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.**Tra**nsportHttp.connect(**TransportHt **tp.java:496) at org.eclipse.jgit.transport.**Tra**nsportHttp.openFetch(**Transport* *Http.java:305) at org.eclipse.jgit.transport.**Fet**chProcess.executeImp(**FetchProc
Re: GIT stopped working after upgrading the plugin to version 1.3.0
I'd almost like to have channels like debian, stable, testing and unstable, it would be very useful (but perhaps too complex to start out that way). I've currently just been putting the hpi/jpi out there for people to download and install, but it would be nice to have something in Jenkins release process. On Thu, Mar 21, 2013 at 10:30 AM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) kpflem...@bloomberg.net wrote: Being a relative newbie here I'm a bit hesitant to throw this out... but with the massive growth in the Jenkins community over the last year or more, maybe it's time to consider having a 'stable' and 'unstable' plugin repositories as well. Developers need ways to test out new things (like has been done with the Git plugins), but users also need ways to stick with plugins that they are comfortable with. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Mar 21 2013 13:23:29 right, there is no LTS concept for plugins 2013/3/21 Aldo Brucale bruc...@gmail.com So also the LTS version of Jenkins pulls the latest version of the plugins. I thought it was safe to keep them updated... On Thursday, 21 March 2013 17:03:29 UTC+1, Nicolas De loof wrote: There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bru...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.**gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/** workspa**ce/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/**workspa**ce/Megapixel_04.07.00 - hudson.remoting.Channel@**61df09**2e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/**megapi** xel/my_build_tools.git https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.**GitExceptio**n: org.eclipse.jgit.api.errors.**Tr* *ansportException: https://git.example.com/**megapi** xel/my_build_tools.git https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.**gitclien**t.JGitAPIImpl.fetch(**JGitAPIImp **l.java:212) at hudson.plugins.git.GitAPI.**fetc**h(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.**in**voke(GitSCM.java:941) at hudson.FilePath$**FileCallableWr**apper.call(**FilePath.java:2246) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:118) at hudson.remoting.UserRequest.**pe**rform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.**InterceptingEx**ecutorService$1.**call(** Intercept**ingExecutorService.**java:72) at java.util.concurrent.**FutureTas**k$Sync.innerRun(**FutureTask.** java:303) at java.util.concurrent.**FutureTas**k.run(FutureTask.**java:138) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.**runTask(** ThreadPoolExecutor.**java:886) at java.util.concurrent.**ThreadPoo**lExecutor$Worker.run(**ThreadPoo **lExecutor.java:908) at java.lang.Thread.run(Thread.**ja**va:619) Caused by: org.eclipse.jgit.api.errors.**Tr**ansportException: https://git.example.com/**megapi**xel/my_build_tools.git https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.**FetchComm**and.call(**FetchCommand.java:** 137) at
Re: GIT stopped working after upgrading the plugin to version 1.3.0
Maybe (implementation would be hard) plugins can tag their highest allowed release. That way, whatever plugin could say, if you're on LTS, this is the auto installed version Andrew Melo Sent from my secret fortress. On Mar 21, 2013, at 12:29, Slide slide.o@gmail.com wrote: I've often wished there was a way to do this though. On Thu, Mar 21, 2013 at 10:22 AM, nicolas de loof nicolas.del...@gmail.com wrote: right, there is no LTS concept for plugins 2013/3/21 Aldo Brucale bruc...@gmail.com So also the LTS version of Jenkins pulls the latest version of the plugins. I thought it was safe to keep them updated... On Thursday, 21 March 2013 17:03:29 UTC+1, Nicolas De loof wrote: There is a bunch of them in bugtracker. I've just released git-client 1.0.5, that will use git-cli by default. will still maintain a JGit implementation, and try to get unit test to reproduce those various issues, but probably will have to wait for next major JGit version - JGit for sample don't support symlinks, cause they only require java 6 :'( 2013/3/21 Aldo Brucale bru...@gmail.com Thank you, I've added -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true for all the slaves end now everything works fine. Is the issue with the git Client Plugin already on the bugtracker? On Thursday, 21 March 2013 16:06:50 UTC+1, Peter Miklosko wrote: Not issue of Git Plugin but git Client Plugin. This been upgraded to 1.0.4 and is messing up as I discovered few days ago http://goo.gl/QKP0H Peter On 21 March 2013 14:54, Aldo Brucale bru...@gmail.com wrote: Hi, I'm running Jenkins LTS (1.480.3) and after upgrading the plugins today Jenkins has stopped downloading the changes from my git server. It seems that jenkins is not accepting the self-signed certificate from the server any more. Any ideas on how to resolve this? I've tried to downgrade the plugin back to version 1.2.0 but nothing has changed. Maybe some dependency has been updated and downgrading the plugin is not sufficient to revert to the previous situation? Thank you in advance, Aldo here is the stacktrace: Building remotely on Montavista in workspace /mnt/montavista/hudson/workspace/Megapixel_04.07.00 Checkout:Megapixel_04.07.00 / /mnt/montavista/hudson/workspace/Megapixel_04.07.00 - hudson.remoting.Channel@61df092e:Montavista Using strategy: Default Last Built Revision: Revision bd975b4d348b588ce3862f91dcd37e109193e799 (origin/04.07.00) Cloning the remote Git repository Cloning repository https://git.example.com/megapixel/my_build_tools.git git --version git version 1.7.2.3 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2246) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.eclipse.jgit.api.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 13 more Caused by: org.eclipse.jgit.errors.TransportException: https://git.example.com/megapixel/my_build_tools.git: cannot open git-upload-pack at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:496) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 14 more Caused by: javax.net.ssl.SSLHandshakeException:
Re: Maven jenkins build is throwing exception.
Hi Eric, I am not using Poll feature at all... I have this build scheduled with Manual JOB only. But still i am getting this exception I don't see any workaround on this problem I am stuck really and don't know how to resolve this problem If you can give me some other workaround to fix this issue that will be great Thanks. On Thursday, March 21, 2013 10:06:37 AM UTC-7, Eric Pyle wrote: Sorry, I don't know when it may be fixed. I am not involved in working on it. As for a workaround, the bug reporter says if the build is manually started, it succeeds - not sure if you've tried that. To still have builds triggered automatically, you could set up a post-commit hook in your source control system to trigger builds when changes are committed. Details depend on which SCM you use. For Git, see http://blog.cloudbees.com/2011/11/polling-must-die-triggering-jenkins.html. Regards, Eric On 3/21/2013 12:29 PM, devanand wrote: Hi Eric, When should i expect to be resolved this BUG ? or is there any work around to this problem ??? Thanks. On Thursday, March 21, 2013 5:28:58 AM UTC-7, Eric Pyle wrote: This is JENKINS-15642.https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric On 3/20/2013 8:34 PM, devanand wrote: Hi, I am getting following exception even though i can see my build is successfull. I can see on local box this has artifact available but still i can see this error whenever i run my jenkins maven build job Please check the attachment of configuration which i am doingn for this project... Please help me to find out the problem I think this is Jenkins Plugin problem or correct me if any other configuration i need to do here INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.602s [INFO] Finished at: Wed Mar 20 17:28:49 PDT 2013 [INFO] Final Memory: 10M/156M [INFO] [JENKINS] Archiving disabled Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 cause : Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at
Re: Maven jenkins build is throwing exception.
Hi Eric, Just a UPDATE on this one I was trying to create a JOB as*Build a maven2/3 project*And it was throwing this exceptions so basically this feature is not stable and not working at all to create successful builds. I tried with *Build a free-style software project* And same commands worked for me to setup automated build for Maven project *So work around is to use free-style software project* Looks like MAVEN plugin is not stable and not working upto date at all... Somebody need to test this completely :) Thanks. On Thursday, March 21, 2013 11:03:30 AM UTC-7, devanand wrote: Hi Eric, I am not using Poll feature at all... I have this build scheduled with Manual JOB only. But still i am getting this exception I don't see any workaround on this problem I am stuck really and don't know how to resolve this problem If you can give me some other workaround to fix this issue that will be great Thanks. On Thursday, March 21, 2013 10:06:37 AM UTC-7, Eric Pyle wrote: Sorry, I don't know when it may be fixed. I am not involved in working on it. As for a workaround, the bug reporter says if the build is manually started, it succeeds - not sure if you've tried that. To still have builds triggered automatically, you could set up a post-commit hook in your source control system to trigger builds when changes are committed. Details depend on which SCM you use. For Git, see http://blog.cloudbees.com/2011/11/polling-must-die-triggering-jenkins.html. Regards, Eric On 3/21/2013 12:29 PM, devanand wrote: Hi Eric, When should i expect to be resolved this BUG ? or is there any work around to this problem ??? Thanks. On Thursday, March 21, 2013 5:28:58 AM UTC-7, Eric Pyle wrote: This is JENKINS-15642.https://issues.jenkins-ci.org/browse/JENKINS-15642 Eric On 3/20/2013 8:34 PM, devanand wrote: Hi, I am getting following exception even though i can see my build is successfull. I can see on local box this has artifact available but still i can see this error whenever i run my jenkins maven build job Please check the attachment of configuration which i am doingn for this project... Please help me to find out the problem I think this is Jenkins Plugin problem or correct me if any other configuration i need to do here INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.602s [INFO] Finished at: Wed Mar 20 17:28:49 PDT 2013 [INFO] Final Memory: 10M/156M [INFO] [JENKINS] Archiving disabled Waiting for Jenkins to finish collecting data mavenExecutionResult exceptions not empty message : Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 cause : Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 Stack trace : org.apache.maven.InternalErrorException: Internal error: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #31 ASC: lo=31,hi=0,size=31,size2=31 at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at
Re: Build of first commit on git branch does not show changes
Kevin, I agree with you. How can that be implemented? All, It appears to me that Jenkins does not work well with this use case: * master HEAD is release version 1 (v1) of product. * 4 features ABCD that are implemented on git branches ABCD respectively based on v1 * Jenkins project to build every branch * Changes are implemented with one commit per branch (developers are exceptional) * Changes are merged without conflict to master as version 2 (v2) How do I get Jenkins to tell me that v2 contains JIRA issues ABCD without scripting this myself? The git plugin does not see any changes when ABCD are built and when v2 is created. Am I outside the assumed use cases of Jenkins/git here? Brian -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: GIT stopped working after upgrading the plugin to version 1.3.0
On 21 March 2013 17:40, Andrew Melo andrew.m...@gmail.com wrote: Maybe (implementation would be hard) plugins can tag their highest allowed release. That way, whatever plugin could say, if you're on LTS, this is the auto installed version +1 Sounds great to me! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins batch command error : ...system cannot find the file specified...
Hello, My environment is Jenkins1.506/VSTFS2010 I was testing Add Build Step for MSBuild Plug-In with a simple Execute Windows batch command and got this: [GAtest1] $ cmd /c call C:\Windows\TEMP\hudson8854542679623085192.bat C:\Program Files (x86)\Jenkins\workspace\GAtest1echo test test C:\Program Files (x86)\Jenkins\workspace\GAtest1COPY D:\drop\test.txt D:\testdir\ *The system cannot find the file specified.* * * The build was successful and the echo command was good, except the COPY command. Anyone has this same issue before? Thanks, -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins batch command error : ...system cannot find the file specified...
Thanks for your response Mark, No, I created the \testdir and test.txt in D:\ to test, they are there, and I also checked the spaces in the command. The funny thing is I did a COPY and CALL command before, in my previous job with similar environment, and Jenkins had no problem at all. Currently, I tried double and single quote and Jenkins still insist on not seeing the file. I sure don't have problem running this command on the dos prompt. On Thursday, March 21, 2013 3:46:19 PM UTC-7, Mark Waite wrote: I think that is saying that the built-in command COPY in the Windows command processor tried to copy from D:\drop\test.txt to D:\testdir\ and either found that D:\drop\test.txt did not exist, or D:\testdir\ did not exist. The preceding echo command did not create D:\drop\test.txt, so I assume it might not exist. The preceding echo command did not create D:\testdir\, so I assume it might not exist as well. Mark Waite -- *From:* dmatrix micha...@gmail.com javascript: *To:* jenkins...@googlegroups.com javascript: *Sent:* Thursday, March 21, 2013 3:57 PM *Subject:* Jenkins batch command error : ...system cannot find the file specified... Hello, My environment is Jenkins1.506/VSTFS2010 I was testing Add Build Step for MSBuild Plug-In with a simple Execute Windows batch command and got this: [GAtest1] $ cmd /c call C:\Windows\TEMP\hudson8854542679623085192.bat C:\Program Files (x86)\Jenkins\workspace\GAtest1echo test test C:\Program Files (x86)\Jenkins\workspace\GAtest1COPY D:\drop\test.txt D:\testdir\ *The system cannot find the file specified.* * * The build was successful and the echo command was good, except the COPY command. Anyone has this same issue before? Thanks, -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins batch command error : ...system cannot find the file specified...
Thanks for your response Mark, No, I created the \testdir and test.txt in D:\ to test, they are there, and I also checked the spaces in the command. The funny thing is I did a COPY and CALL command before, in my previous job with similar environment, and Jenkins had no problem at all. Currently, I tried double and single quote and Jenkins still insist on not seeing the file. I sure don't have problem running this command on the dos prompt. On Thursday, March 21, 2013 3:46:19 PM UTC-7, Mark Waite wrote: I think that is saying that the built-in command COPY in the Windows command processor tried to copy from D:\drop\test.txt to D:\testdir\ and either found that D:\drop\test.txt did not exist, or D:\testdir\ did not exist. The preceding echo command did not create D:\drop\test.txt, so I assume it might not exist. The preceding echo command did not create D:\testdir\, so I assume it might not exist as well. Mark Waite -- *From:* dmatrix micha...@gmail.com javascript: *To:* jenkins...@googlegroups.com javascript: *Sent:* Thursday, March 21, 2013 3:57 PM *Subject:* Jenkins batch command error : ...system cannot find the file specified... Hello, My environment is Jenkins1.506/VSTFS2010 I was testing Add Build Step for MSBuild Plug-In with a simple Execute Windows batch command and got this: [GAtest1] $ cmd /c call C:\Windows\TEMP\hudson8854542679623085192.bat C:\Program Files (x86)\Jenkins\workspace\GAtest1echo test test C:\Program Files (x86)\Jenkins\workspace\GAtest1COPY D:\drop\test.txt D:\testdir\ *The system cannot find the file specified.* * * The build was successful and the echo command was good, except the COPY command. Anyone has this same issue before? Thanks, -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
jenkins plugin exec master,but not slaver execute?
Hi, Kohsuke
I write a plugin.It‘s function; svn checkout then exec assign build。
my test code:
public class CheckoutTask implements FileCallableBoolean {
public Boolean invoke(File workspace, VirtualChannel channel)
throws IOException {
// This here code is executed on the slave.
// Call the library method to check out the files
System.out.print(aaa);
return true;
}
}
public boolean checkout(AbstractBuild build, Launcher launcher,
FilePath workspace, BuildListener listener) throws IOException,
InterruptedException {
final long serialVersionUID = 8158155902777163137L;
CheckoutTask task = new CheckoutTask();
return workspace.act(task); // The CheckoutTask.invoke() method is
now
// invoked
}
Exception:
hudson.util.IOException2: remote file operation failed:
e:\JenkinsHome-2\workspace\c at hudson.remoting.Channel@10f932a:test-89
at hudson.FilePath.act(FilePath.java:779)
at hudson.FilePath.act(FilePath.java:765)
at
com.mycom.scm.jenkins.plugins.IfmConfigBuilder.checkout(IfmConfigBuilder.java:470)
at
com.mycom.scm.jenkins.plugins.IfmConfigBuilder.perform(IfmConfigBuilder.java:152)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462)
at hudson.model.Run.run(Run.java:1404)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: java.io.IOException: Unable to serialize
hudson.FilePath$FileCallableWrapper@1c806f3
at hudson.remoting.UserRequest.serialize(UserRequest.java:166)
at hudson.remoting.UserRequest.init(UserRequest.java:62)
at hudson.remoting.Channel.call(Channel.java:680)
at hudson.FilePath.act(FilePath.java:772)
... 12 more
Caused by: java.io.NotSerializableException:
com.mycom.scm.jenkins.plugins.IfmConfigBuilder
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346)
at hudson.remoting.UserRequest._serialize(UserRequest.java:155)
at hudson.remoting.UserRequest.serialize(UserRequest.java:164)
... 15 more
IfmConfigBuilder perform execMain method is error!三月 22, 2013 9:55:07 上午
hudson.model.Run run
信息: c #23 main build action completed: SUCCESS
weibo: http://www.weibo.com/u/2158124217 http://weibo.com/n/codyzhang
Best Regards，
--Cody.Zhang
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
AVD exception in Jenkins
Hi, I was tried to run build with AVD in jenkins with below configuration. nabble_img src=jenkins.png border=0 class=center alt=Configuration/ But , when I build the job, I got below exception. What I need to do.. [android] Failed to run AVD creation command Exception in thread main java.lang.NullPointerException at com.android.sdklib.internal.avd.AvdManager.parseAvdInfo(AvdManager.java:1387) at com.android.sdklib.internal.avd.AvdManager.buildAvdList(AvdManager.java:1366) at com.android.sdklib.internal.avd.AvdManager.init(AvdManager.java:315) at com.android.sdklib.internal.avd.AvdManager.getInstance(AvdManager.java:325) at com.android.sdkmanager.Main.createAvd(Main.java:1100) at com.android.sdkmanager.Main.doAction(Main.java:268) at com.android.sdkmanager.Main.run(Main.java:119) at com.android.sdkmanager.Main.main(Main.java:102) [android] Could not create Android emulator: Failed to run AVD creation command -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
svn update not working with jar and zip file - quick question
Hi All Has anyone experience of svn updates not working with jar and zip files ? We experience this where for unclear reason the jar or zip file would not update with newer jar and zip files in SVN after issuing a SCM checkout from Jenkins in a job. How do we come this problem ? Thanks All -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
