Would it help if this was added to the prepare.groovy?
try
{
"""svn upgrade""".execute()
}
catch( Exception e )
{
// noop, no need to upgrade
}
return true
I seem to have a matching client version, so the IT works on my system.
Could someone verify the code above?
thanks,
Robert
Op Tue, 06 May 2014 08:43:45 +0200 schreef Dan Tran <dant...@gmail.com>:
perhaps, we need to disable this specific test for now?
-D
On Mon, May 5, 2014 at 9:18 PM, Dan Tran <dant...@gmail.com> wrote:
Looks like we stuck without a new snapshot until this is fixed!!
-D
On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY
<herve.bout...@free.fr>wrote:
seems related to SCM-741: the IT added contains a copy of .svn content
taken
from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has
a
different one (format 31)
don't know how wa can improve the IT to be more tolerant to svn version
updates
Regards,
Hervé
Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit :
> change list https://builds.apache.org/job/maven-scm/changes
>
> -D
>
> On Mon, May 5, 2014 at 9:01 AM, Dan Tran <dant...@gmail.com> wrote:
> > https://builds.apache.org/job/maven-scm/
> >
> > Thanks
> >
> > -D
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
