AFAIK Hudson should detect the SVN changes and start a build then.
However somethings broken. See
http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/scmPollLog/
Jukka, could you have a look?
Michael
Last Subversion Polling Log
Started on Mar 26, 2010 8:01:08 AM
SSH channel is closed. (Close requested by remote)
java.io.IOException: SSH channel is closed. (Close requested by remote)
at
com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:383)
at
com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63)
at
java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1838)
at
java.io.ObjectOutputStream$BlockDataOutputStream.writeByte(ObjectOutputStream.java:1876)
at
java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1537)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:329)
at hudson.remoting.Channel.send(Channel.java:417)
at hudson.remoting.Request.call(Request.java:105)
at hudson.remoting.Channel.call(Channel.java:551)
at hudson.scm.SubversionSCM.pollChanges(SubversionSCM.java:1054)
at
hudson.model.AbstractProject.pollSCMChanges(AbstractProject.java:1076)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:319)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:346)
at
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Done. Took 0.18 sec
No changes
On 3/26/10 8:39 AM, Tobias Bocanegra wrote:
when/how is hudson triggered to build jackrabbit again?
the last build is 1 1/2 days old.
regards, toby
On Thu, Mar 25, 2010 at 2:21 PM, Tobias Bocanegra<[email protected]> wrote:
i'll have a look at it.
regards, toby
On Thu, Mar 25, 2010 at 12:36 PM, Michael Dürig<[email protected]> wrote:
These test failures seem to be caused by the changes done in JCR-2582.
Michael
On 3/24/10 3:00 PM, Apache Hudson Server wrote:
See<http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1094/>