Hi, Hmm. How do other projects using VMBuild solve this issue ?
A CI system IMHO is of limited use if the built artifacts are not deployed after a successfull build (yes, just knowing that builds are successfull is valuable in itself). Regards Felix Am Mittwoch, den 12.12.2007, 18:19 +0100 schrieb Carsten Ziegeler: > Ok, obviously I was to optimistic with the deployment :( > The credentials are missing for the deployment, so I will change the > continuum installation to just "install" our modules; deployment has to > be done manually. > > Carsten > > Continuum VMBuild Server wrote: > > Online report : > > http://vmbuild.apache.org/continuum/buildResult.action?buildId=28013&projectId=298 > > > > > > Build statistics: > > State: Failed > > Previous State: Ok > > Started at: Wed 12 Dec 2007 09:06:59 -0800 > > Finished at: Wed 12 Dec 2007 09:12:02 -0800 > > Total time: 5m 2s > > Build Trigger: Schedule > > Build Number: 5 > > Exit code: 1 > > Building machine hostname: vmbuild.apache.org > > Operating system : Linux(unknown) > > Java Home version : java version "1.6.0" > > Java(TM) SE Runtime Environment (build 1.6.0-b105) > > Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing) > > Builder version : > > Maven version: 2.0.7 > > Java version: 1.6.0 > > OS name: "linux" version: "2.6.20-16-server" arch: "i386" > > > > > > >
