AntUnit @ Jenkins
The job is ready. But the last build gives me an error: https://builds.apache.org/view/A-D/view/Ant/job/AntLib-antunit/lastBuild/con sole [au:antunit] Build File: /x1/jenkins/jenkins-slave/workspace/AntLib-antunit/src/tests/antunit/assertR esourceExists-test.xml [au:antunit] Tests run: 4, Failures: 2, Errors: 0, Time elapsed: 0.488 sec [au:antunit] Target: testURLUsingRef-no FAILED [au:antunit] at line 45, column 59 [au:antunit] Message: Didn't expect resource 'antsite-foo' to exist [au:antunit] took 0.003 sec [au:antunit] Target: testURL took 0.001 sec [au:antunit] Target: testURL-no FAILED [au:antunit] at line 37, column 41 [au:antunit] Message: Didn't expect resource to exist [au:antunit] took 0.196 sec The tests check that the given URL does not exist (which gives me a 404 in the browser and my local au-tests pass). target name=testURL-no description=https://issues.apache.org/bugzilla/show_bug.cgi?id=53383; au:assertNestedResourceDoesntExist url url=http://ant.apache.org/foo.html/ /au:assertNestedResourceDoesntExist /target target name=testURLUsingRef-no description=https://issues.apache.org/bugzilla/show_bug.cgi?id=53383; url url=http://ant.apache.org/foo.html; id=antsite-foo/ au:assertRefResourceDoesntExist refid=antsite-foo/ /target Is this related to the Jenkins-environment? Jan
AntLib-svn @ Jenkins
AntLib-SVN ist running on Jenkins now without problems. https://builds.apache.org/job/AntLib-svn https://builds.apache.org/job/AntLib-svn/lastBuild/console Jan
Re: AW: Repository access
I do not think each commiter needs to do that but if you and Jean-Louis go
through this exercise and create an INFRA ticket that would be very nice. As
for me I have a lot of work in my day job and on top of that I have caught an
out of season cold, with the temperature in New York going up and down and too
much air conditioning at some places.
Regards,
Antoine
Le 6 juin 2014 01:08, =?ISO-8859-1?Q?Jan_Mat=E8rne_=28jhm=29?=
apa...@materne.de a écrit :
Should we (each committer) try to commit/push to each repo before creating
the issue?
Maybe creating one file/repo (./git-access-test) where each committer places
his name.
Retest after the issue is resolved and finally delete that file.
In that way INFRA doesnt need to act multiple times ...
Jan
-Ursprüngliche Nachricht-
Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
Gesendet: Freitag, 6. Juni 2014 03:21
An: Ant Developers List
Betreff: Re: Repository access
Hello Jean-Louis,
please create the JIRA,
Antoine
On Jun 5, 2014, at 3:03 PM, Jean-Louis Boudart
jeanlouis.boud...@gmail.com wrote:
Same for me is there other repos having same issue?
We need to create a INFRA jira for this.
2014-06-05 18:08 GMT+02:00 Nicolas Lalevée
nicolas.lale...@hibnet.org:
I couldn't commit the patch you suggested for the ivyde updatesite
in
svn either. It must be read only.
Nicolas
Le 5 juin 2014 à 07:57, Jan Matèrne (jhm) apa...@materne.de a
écrit :
After ivyde-updatesite (svn) this is the 2nd repo where I can't
commit/push
https://git-wip-us.apache.org/repos/asf/easyant-core.git
Is there any reason?
Jan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For
additional
commands, e-mail: dev-h...@ant.apache.org
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: AW: Repository access
Can we not work with pull requests, in Git? At least this is an approach when working in GitHub. André-John Sent from my phone. Envoyé depuis mon téléphone. On 6 Jun 2014, at 12:19, Antoine Levy-Lambert anto...@gmx.de wrote: I do not think each commiter needs to do that but if you and Jean-Louis go through this exercise and create an INFRA ticket that would be very nice. As for me I have a lot of work in my day job and on top of that I have caught an out of season cold, with the temperature in New York going up and down and too much air conditioning at some places. Regards, Antoine Le 6 juin 2014 01:08, =?ISO-8859-1?Q?Jan_Mat=E8rne_=28jhm=29?= apa...@materne.de a écrit : Should we (each committer) try to commit/push to each repo before creating the issue? Maybe creating one file/repo (./git-access-test) where each committer places his name. Retest after the issue is resolved and finally delete that file. In that way INFRA doesnt need to act multiple times ... Jan -Ursprüngliche Nachricht- Von: Antoine Levy Lambert [mailto:anto...@gmx.de] Gesendet: Freitag, 6. Juni 2014 03:21 An: Ant Developers List Betreff: Re: Repository access Hello Jean-Louis, please create the JIRA, Antoine On Jun 5, 2014, at 3:03 PM, Jean-Louis Boudart jeanlouis.boud...@gmail.com wrote: Same for me is there other repos having same issue? We need to create a INFRA jira for this. 2014-06-05 18:08 GMT+02:00 Nicolas Lalevée nicolas.lale...@hibnet.org: I couldn't commit the patch you suggested for the ivyde updatesite in svn either. It must be read only. Nicolas Le 5 juin 2014 à 07:57, Jan Matèrne (jhm) apa...@materne.de a écrit : After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push https://git-wip-us.apache.org/repos/asf/easyant-core.git Is there any reason? Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org -- Jean Louis Boudart Independent consultant Apache EasyAnt commiter http://ant.apache.org/easyant/ - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
