You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2015/01/23 05:21:24 UTC
Build failed in Jenkins: Roller #1497
See <https://builds.apache.org/job/Roller/1497/>
------------------------------------------
Started by timer
Building remotely on solaris1 (Solaris) in workspace <https://builds.apache.org/job/Roller/ws/>
Updating https://svn.apache.org/repos/asf/roller/trunk at revision '2015-01-23T04:17:00.542 +0000'
U docs/testing/junit-cleartables-mysql.sql
A docs/testing/roller-junit.properties
U app/src/test/java/org/apache/roller/weblogger/business/MediaFileTest.java
U app/src/main/java/org/apache/roller/weblogger/pojos/MediaFile.java
U app/src/main/java/org/apache/roller/weblogger/business/FileContentManagerImpl.java
U app/src/main/java/org/apache/roller/weblogger/ui/struts2/editor/MediaFileBean.java
U app/src/main/java/org/apache/roller/weblogger/TestUtils.java
At revision 1654112
no change for https://svn.apache.org/repos/asf/roller/trunk since the previous build
Parsing POMs
maven3-agent.jar already up to date
maven3-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Roller] $ /home/jenkins/tools/java/latest1.7/bin/java -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp /export/home/hudson/hudson-slave/maven3-agent.jar:/export/home/hudson/hudson-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /export/home/hudson/hudson-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 /zonestorage/hudson_solaris/home/hudson/hudson-slave/slave.jar /export/home/hudson/hudson-slave/maven3-interceptor.jar /export/home/hudson/hudson-slave/maven3-interceptor-commons.jar 45594
ERROR: Failed to parse POMs
java.io.IOException: Cannot run program "/home/jenkins/tools/java/latest1.7/bin/java" (in directory "<https://builds.apache.org/job/Roller/ws/")>: error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at hudson.Proc$LocalProc.<init>(Proc.java:244)
at hudson.Proc$LocalProc.<init>(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:780)
at hudson.Launcher$ProcStarter.start(Launcher.java:360)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1111)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1078)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
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.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
... 15 more
Re: Fwd: Jenkins build is back to normal : Roller #1498
Posted by Greg Huber <gr...@gmail.com>.
I was more thinking of saving resources, and unnecessary emails, rebuilding
a project that has not changed (for weeks) is just an unnecessary
overhead. Doing a SCM pole is much less.
Cheers Greg.
On 23 January 2015 at 10:32, Glen Mazza <gl...@gmail.com> wrote:
> I'm unsure what the other projects do but I think the status quo is OK.
> We only get a message that everything is OK after a failure, and sometimes
> it's good to get failures because they point to problems outside of the
> code but in the Jenkins process. We may go another three weeks with no
> emails due to consecutive success builds.
>
> Glen
>
> On 01/23/2015 03:59 AM, Greg Huber wrote:
>
>> Can we not poll the SCM and if there are changes do the build, rather than
>> running it every day regardless of changes?
>>
>> Cheers Greg.
>>
>>
>> ---------- Forwarded message ----------
>> From: Apache Jenkins Server <je...@builds.apache.org>
>> Date: 23 January 2015 at 08:55
>> Subject: Jenkins build is back to normal : Roller #1498
>> To: dev@roller.apache.org, glen.mazza@gmail.com
>>
>>
>> See <https://builds.apache.org/job/Roller/1498/>
>>
>>
>
Re: Fwd: Jenkins build is back to normal : Roller #1498
Posted by Glen Mazza <gl...@gmail.com>.
I'm unsure what the other projects do but I think the status quo is OK.
We only get a message that everything is OK after a failure, and
sometimes it's good to get failures because they point to problems
outside of the code but in the Jenkins process. We may go another three
weeks with no emails due to consecutive success builds.
Glen
On 01/23/2015 03:59 AM, Greg Huber wrote:
> Can we not poll the SCM and if there are changes do the build, rather than
> running it every day regardless of changes?
>
> Cheers Greg.
>
>
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <je...@builds.apache.org>
> Date: 23 January 2015 at 08:55
> Subject: Jenkins build is back to normal : Roller #1498
> To: dev@roller.apache.org, glen.mazza@gmail.com
>
>
> See <https://builds.apache.org/job/Roller/1498/>
>
Fwd: Jenkins build is back to normal : Roller #1498
Posted by Greg Huber <gr...@gmail.com>.
Can we not poll the SCM and if there are changes do the build, rather than
running it every day regardless of changes?
Cheers Greg.
---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: 23 January 2015 at 08:55
Subject: Jenkins build is back to normal : Roller #1498
To: dev@roller.apache.org, glen.mazza@gmail.com
See <https://builds.apache.org/job/Roller/1498/>
Jenkins build is back to normal : Roller #1498
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Roller/1498/>