You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Eelco Hillenius <ee...@gmail.com> on 2007/04/27 07:07:29 UTC
bamboo problems svn repository locked
Hi all,
I can't get bamboo to do a fresh build. It tries to update from svn,
but then complains that the SVN repository is locked. It says it will
issue a cleanup request for the next build, which is does, but after
that it's still not able to update. Maybe it helps if someone does an
explicit svn cleanup? And is there anyway we can avoid this in the
future after it is fixed? It's kind of icky that Bamboo doesn't fail/
halts the build, as the jar is updated in our maven repo and the only
way I can tell it's still and old one is because I get compile errors.
Eelco
Re: bamboo problems svn repository locked
Posted by Eelco Hillenius <ee...@gmail.com>.
Cool, thanks.
Eelco
On 4/27/07, Johan Compagner <jc...@gmail.com> wrote:
> a delete of all the build files seems to do the trick.
>
>
> On 4/27/07, Eelco Hillenius <ee...@gmail.com> wrote:
> >
> > Hi all,
> >
> > I can't get bamboo to do a fresh build. It tries to update from svn,
> > but then complains that the SVN repository is locked. It says it will
> > issue a cleanup request for the next build, which is does, but after
> > that it's still not able to update. Maybe it helps if someone does an
> > explicit svn cleanup? And is there anyway we can avoid this in the
> > future after it is fixed? It's kind of icky that Bamboo doesn't fail/
> > halts the build, as the jar is updated in our maven repo and the only
> > way I can tell it's still and old one is because I get compile errors.
> >
> > Eelco
> >
>
Re: bamboo problems svn repository locked
Posted by Johan Compagner <jc...@gmail.com>.
a delete of all the build files seems to do the trick.
On 4/27/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> Hi all,
>
> I can't get bamboo to do a fresh build. It tries to update from svn,
> but then complains that the SVN repository is locked. It says it will
> issue a cleanup request for the next build, which is does, but after
> that it's still not able to update. Maybe it helps if someone does an
> explicit svn cleanup? And is there anyway we can avoid this in the
> future after it is fixed? It's kind of icky that Bamboo doesn't fail/
> halts the build, as the jar is updated in our maven repo and the only
> way I can tell it's still and old one is because I get compile errors.
>
> Eelco
>