The failing build is due to the non-standard maven repository. The build is made on a ubuntu-slave which has its own local repostry at a custom location. This setting is paassed in the build eg in d build 45 the local repos was set as -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1
On Sun, Jul 7, 2013 at 3:13 PM, Andrei Savu <[email protected]> wrote: > No idea why this is happening. Maybe due to file size? > > I think we need to report this on [email protected] or on INFRA JIRA. > > -- Andrei Savu > > On Sat, Jul 6, 2013 at 5:48 PM, Rahul Sharma <[email protected]> wrote: > > > The build has just one test failure.It is not able to find the artifact > > being referred in one of the tests. The artifact gets built but it is > > install on one of the slaves and for some reason the test is trying to > find > > it on master, which is giving the error. Any ideas on how to fix this ? > > > > regards > > Rahul > > > > > > On Sat, Jul 6, 2013 at 6:39 AM, Apache Jenkins Server < > > [email protected]> wrote: > > > > > See <https://builds.apache.org/job/provisionr-master/43/> > > > > > > > > >
