+1 with Robert's solution (though I don't remember it was the actual issue
for that ci build failure some weeks ago...).
That's something I've also been planning to do after working recently with
buildnumber. BTW, not sure yet why, but sometimes IT won't fail doing a svn
info under the hood althou
ASF Jenkins has some hikkups these days + now the mail outage =
since last time, I coded the svn upgrade thing, and I even downgraded the .svn
directory in sources to svn 1.6 to match version used by ASF Jenkins
everything should be ok now on this front
on the ASF Jenkins front, problems are so
This issue is very stubborn -)
I saw Hervé make a few changes, but builds.apache.org also have not
triggered a new build? what is the schedule for this job?
-Dan
On Thu, May 8, 2014 at 9:25 AM, Robert Scholte wrote:
> it's probably something like .execute( null, basedir ) to ensure the righ
Yes, it is a better approach since the build is currently falling at ubuntu
build at builds.apache.org
-D
On Tue, May 6, 2014 at 3:14 PM, Hervé BOUTEMY wrote:
> I think Roberts' idea about "svu upgrade"ing is good
> just need to revert locally and test, or we'll get the same problem in some
>
it's probably something like .execute( null, basedir ) to ensure the right
working directory is used.
Robert
http://groovy.codehaus.org/groovy-jdk/java/lang/String.html#execute%28java.util.List,%20java.io.File%29
Op Wed, 07 May 2014 00:14:07 +0200 schreef Hervé BOUTEMY
:
I think Roberts
I think Roberts' idea about "svu upgrade"ing is good
just need to revert locally and test, or we'll get the same problem in some
time, when svn 1.9 is out
Regards,
Hervé
Le mardi 6 mai 2014 15:00:58 Dan Tran a écrit :
> Thanks Hervé, it works on my local windows build with svn client 1.8.5
>
Thanks Hervé, it works on my local windows build with svn client 1.8.5
-D
On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY wrote:
> I updated content to svn 1.8: not really a long term solution, but at least
> give us time to find a better solution
>
> Regards,
>
> Hervé
>
> Le lundi 5 mai 2014
Just tried it and still failing ( but not known why yet)
[INFO] --- maven-invoker-plugin:1.8:run (integration-test) @
maven-scm-plugin ---
[INFO] Building: scm-741-validate-scm-url-matches-working-copy\pom.xml
[INFO] run script prepare.groovy
[INFO] ..FAILED (6.6 s)
[INFO] The build exited with
I updated content to svn 1.8: not really a long term solution, but at least
give us time to find a better solution
Regards,
Hervé
Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit :
> perhaps, we need to disable this specific test for now?
>
> -D
>
> On Mon, May 5, 2014 at 9:18 PM, Dan Tran wrot
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,
perhaps, we need to disable this specific test for now?
-D
On Mon, May 5, 2014 at 9:18 PM, Dan Tran 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 wrote:
>
>> seems related to SCM-741: the IT added contains
Looks like we stuck without a new snapshot until this is fixed!!
-D
On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY 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 (
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 0
change list https://builds.apache.org/job/maven-scm/changes
-D
On Mon, May 5, 2014 at 9:01 AM, Dan Tran wrote:
>
>
>
> https://builds.apache.org/job/maven-scm/
>
> Thanks
>
> -D
>
https://builds.apache.org/job/maven-scm/
Thanks
-D
15 matches
Mail list logo
