[JIRA] (JENKINS-16808) deployment of more files
Javatar007 commented on JENKINS-16808 deployment of more files Trying to update the plugin, getting error 'archive is not a ZIP archive'. I don't know if the problem is on my side :S Raphael, could you please verify the plugin format is correct? 7 mars 2013 14:44:43 jenkins.InitReactorRunner$1 onTaskFailed GRAVE: Failed Inspecting plugin C:\Users\xixao\.jenkins\plugins\weblogic-deployer-plugin.jpi hudson.util.IOException2: Failed to expand C:\Users\xixao\.jenkins\plugins\weblogic-deployer-plugin.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:435) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:122) at hudson.PluginManager$1$3$1.run(PluginManager.java:223) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:882) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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: Error while expanding C:\Users\xixao\.jenkins\plugins\weblogic-deployer-plugin.jpi java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:192) at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:433) ... 10 more Caused by: java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:481) at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:320) at org.apache.tools.zip.ZipFile.init(ZipFile.java:186) at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:170) ... 12 more 7 mars 2013 14:44:43 jenkins.InitReactorRunner$1 onAttained This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16808) deployment of more files
Javatar 007 created JENKINS-16808 deployment of more files Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer Created: 14/Feb/13 3:00 PM Description: It would be usefull to enable deployment of multiple files. Imagine a project where several webapp packages are created - e.g. in our big project maven builds several submodules, some of them .ear and .war. We'd like to deploy them all in one jenkins-job. There might be a dynamic list in the plugin's configuration where you put pairs "name"-"file", and the job would undeploydeploy them all in a sequence. Project: Jenkins Labels: deploy maven, weblogic ear war Priority: Major Reporter: Javatar 007 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6567) CLONE -Maven2: AssertionError: reporters.get == null
Javatar 007 reopened JENKINS-6567 CLONE -Maven2: AssertionError: reporters.get == null see comments in the duplicate ticket 1454 Change By: Javatar 007 (31/Jan/13 8:47 AM) Resolution: Duplicate Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-2807) Hudson FATAL error when switching JDK (m2 support)
Javatar 007 reopened JENKINS-2807 Hudson FATAL error when switching JDK (m2 support) See the duplicate issue JENKINS-1454, in version 1.496 it's failing with the same exception. Change By: Javatar 007 (31/Jan/13 8:51 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-1454) Maven2: AssertionError: reporters.get == null
Javatar 007
commented on JENKINS-1454
Maven2: AssertionError: reporters.get == null
I do confirm, in our chain we have in the 2nd job maven target: cobertura:cobertura ${mvn_opts}
And the ${mvn_opts} is set in the 1st job of the chain with maven_opts="-P PROFILE1"
The result:
INFO Preparing cobertura:cobertura
INFO
ERROR FATAL ERROR
INFO
INFO reporters.get(com.bobo:module1)==null. reporters={com.bobo:ROOT=[hudson.maven.reporters.MavenArtifactArchiver@1d838d9, hudson.maven.reporters.MavenSiteArchiver@13d07ff, hudson.maven.reporters.MavenTestJavadocArchiver@1d81be9, hudson.maven.reporters.MavenJavadocArchiver@11081d1, hudson.maven.reporters.SurefireArchiver@baf94e, hudson.maven.reporters.BuildInfoRecorder@14582b8, hudson.maven.reporters.MavenFingerprinter@2ce1f6]} proxies={com.bobo:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a}
INFO
INFO Trace
java.lang.AssertionError: reporters.get(com.bobo:module1)==null. reporters={com.bobo:ROOT=[hudson.maven.reporters.MavenArtifactArchiver@1d838d9, hudson.maven.reporters.MavenSiteArchiver@13d07ff, hudson.maven.reporters.MavenTestJavadocArchiver@1d81be9, hudson.maven.reporters.MavenJavadocArchiver@11081d1, hudson.maven.reporters.SurefireArchiver@baf94e, hudson.maven.reporters.BuildInfoRecorder@14582b8, hudson.maven.reporters.MavenFingerprinter@2ce1f6]} proxies={com.bobo:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a}
at hudson.maven.Maven2Builder.postModule(Maven2Builder.java:126)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:340)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:296)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:185)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:153)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
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)
INFO
INFO Total time: 13 seconds
INFO Finished at: Wed Jan 30 14:59:27 CET 2013
INFO Final Memory: 39M/95M
INFO
En attente que Jenkins finisse de récupérer les données
channel stopped
Finished: FAILURE
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
fvck_u fvck_u commented on JENKINS-6890 clone-workspace-scm doesnt work when source job is a matrix job. I have 2 jobs in my stream, after the first one is completed the 2nd one fails with the same error: Building in workspace C:\Users\myname\.jenkins\workspace\MyJob02 ERROR: MyJob01's most recent build matching the criteria 'Any' doesn't have a workspace snapshot attached. Please run another build in MyJob01 to get the workspace snapshot generated and attached. Finished: FAILURE But when I check the build result: c:\Users\myname\.jenkins\jobs\MyJob01\configurations\builds\2012-11-14_15-46-11\workspace.tar.gz It seems that clone-workspace-scm searches the workspace.tar.gz archive in a wrong folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
