I think it was just issue with 'solaris1' env. On Tue, Feb 14, 2012 at 3:23 PM, Antonio Sanso <[email protected]> wrote:
> Ooops talked too early :) > > Seems working now lol!! > > Thanks again!! > > Antonio > > On Feb 14, 2012, at 3:08 PM, Antonio Sanso wrote: > > > Hu Lukasz, > > > > thanks for setting the mail notification up. > > It seems there is an issue though. Mail seems to be sent on failure but > I do not think anybody received it. See also > > > > > > at hudson.FilePath.act(FilePath.java:784) > > at hudson.FilePath.act(FilePath.java:770) > > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742) > > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684) > > at > hudson.model.AbstractProject.checkout(AbstractProject.java:1195) > > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:576) > > at > hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465) > > at hudson.model.Run.run(Run.java:1409) > > at > hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) > > at > hudson.model.ResourceController.execute(ResourceController.java:88) > > at hudson.model.Executor.run(Executor.java:238) > > Caused by: java.io.IOException: Remote call on solaris1 failed > > at hudson.remoting.Channel.call(Channel.java:690) > > at hudson.FilePath.act(FilePath.java:777) > > ... 10 more > > Caused by: java.lang.ClassFormatError: Failed to load > javax.servlet.ServletException > > at > hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:154) > > at > hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:252) > > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > > at > hudson.scm.SubversionWorkspaceSelector.syncWorkspaceFormatFromMaster(SubversionWorkspaceSelector.java:85) > > at > hudson.scm.SubversionSCM.createSvnClientManager(SubversionSCM.java:822) > > at > hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:765) > > at > hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:752) > > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099) > > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > > at hudson.remoting.Request$2.run(Request.java:287) > > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) > > at java.util.concurrent.FutureTask.run(FutureTask.java:123) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) > > at java.lang.Thread.run(Thread.java:595) > > Caused by: java.lang.UnsupportedClassVersionError: Bad version number in > .class file > > at java.lang.ClassLoader.defineClass1(Native Method) > > at java.lang.ClassLoader.defineClass(ClassLoader.java:621) > > at java.lang.ClassLoader.defineClass(ClassLoader.java:466) > > at > hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:152) > > ... 18 more > > Sending e-mails to: [email protected]<mailto: > [email protected]> > > > > on [0] . > > > > Is there any chance you might give a look into? > > > > Regards > > > > Antonio > > > > > > [0] https://builds.apache.org/job/Amber/37/console > > On Feb 6, 2012, at 2:46 PM, Pid wrote: > > > > On 02/02/2012 12:20, Łukasz Moreń wrote: > > Hi all, > > > > I've fixed 'Failed to deploy artifacts: Could not transfer artifact'. I > can > > setup email notification on failure in Jenkins console. What address > should > > be used? [email protected]<mailto: > [email protected]>? > > > > Yes, sounds good. > > > > > > p > > > > Cheers, > > Lukasz > > > > On Fri, Jan 20, 2012 at 1:37 PM, Antonio Sanso <[email protected]<mailto: > [email protected]>> wrote: > > > > Hi *, > > > > as for AMBER-20 [0] a build profile has been created on Jenkins [1] (and > > this is really good). > > I'd have a couple of question about it: > > > > - at the moment the build is failing. Is there any chance to sort it out? > > The failing reason is not code related: > > " Failed to deploy artifacts: Could not transfer artifact " > > - may we also enable the notification on failure? We can also do it as > > part of AMBER-37 [2] > > > > Thanks > > > > Antonio > > > > > > [0] https://issues.apache.org/jira/browse/AMBER-20 > > [1] https://builds.apache.org/job/Amber/ > > [2] https://issues.apache.org/jira/browse/AMBER-37 > > > > > > > > > > -- > > > > [key:62590808] > > > > > >
