ailto:maarten_co...@yahoo.com.INVALID]
> Gesendet: Mittwoch, 9. November 2016 09:19
> An: Ant Developers List
> Betreff: Fw: Build failed in Jenkins: Ivy-tests » JDK 1.5
> (latest),Windows #157
>
> Anyone an idea why this is failing and can someone fix it?I would try
> to do this m
Anyone an idea why this is failing and can someone fix it?I would try to do
this myself, but I don't have the necessary permissions on Jenkins.
regards,Maarten
- Doorgestuurd bericht -
Van: Apache Jenkins Server
Aan: notificati...@ant.apache.org
Verzonden: woensdag 9 nov
Hi all
it looks as if the configuration for Windows builds will now need a
different version of Ant - something with "Windows" in its name - which
can't be configured via the matrix setup at all.
Given the 1.9.x build already contains totally separate JDKs for Ubuntu
and Windows I'll go ahead and
Hi
the failing builds you've see today come from me trying to console our
Matrix build with
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
I'm starting with the jobs for 1.9.x and will modify master once/iff I
get it working for 1.9.x.
We are now using the "JDK 1.X (la
On 2016-07-11, Stefan Bodewig wrote:
> On 2016-07-11, Stefan Bodewig wrote:
>> On 2016-06-24, Jan Matèrne (jhm) wrote:
>>> I try to understand, why AntUnit is failing on the CI ...
>>> (Works on my Win7 machine).
>> It looks as if the current working directory is not what one would
>> expect. I
On 2016-07-11, Stefan Bodewig wrote:
> On 2016-06-24, Jan Matèrne (jhm) wrote:
>> I try to understand, why AntUnit is failing on the CI ...
>> (Works on my Win7 machine).
> It looks as if the current working directory is not what one would
> expect. In your configuration using "-f" it failed to
On 2016-06-24, Jan Matèrne (jhm) wrote:
> I try to understand, why AntUnit is failing on the CI ...
> (Works on my Win7 machine).
It looks as if the current working directory is not what one would
expect. In your configuration using "-f" it failed to find the build
file, and in my latest attempt
I try to understand, why AntUnit is failing on the CI ...
(Works on my Win7 machine).
Jan
> -Ursprüngliche Nachricht-
> Von: Apache Jenkins Server [mailto:jenk...@builds.apache.org]
> Gesendet: Freitag, 24. Juni 2016 12:40
> An: notificati...@ant.apache.org
> Betreff:
I will take a look too.
Antoine
On Apr 17, 2016, at 1:44 PM, Stefan Bodewig wrote:
> On 2016-04-17, Apache Jenkins Server wrote:
>
>> See
>> <https://builds.apache.org/job/Ant-Build-Matrix-master/jdk=Open%20JDK%201.8%20(Only%20on%20ubuntu%20nodes),label=Ubuntu/851/change
On 2016-04-17, Apache Jenkins Server wrote:
> See
> <https://builds.apache.org/job/Ant-Build-Matrix-master/jdk=Open%20JDK%201.8%20(Only%20on%20ubuntu%20nodes),label=Ubuntu/851/changes>
That's pretty frustrating. SetPermissions doesn't work on Windows (and
the ownedby tes
On 2016-02-25, Antoine Levy Lambert wrote:
> I would like to catch up and make a few contributions to Ant and Ivy.
great!
> I noticed that the Jenkins builds in JDK 1.5 on Ubuntu are failing [1]
> , this is due to a patch recently committed by Stefan [2].
Oops. Broken Windows. I
Hi,
first I have not been working on Ant at all in the last 12 months or more, I
recently changed job and my current work has been very involving.
I would like to catch up and make a few contributions to Ant and Ivy.
I noticed that the Jenkins builds in JDK 1.5 on Ubuntu are failing [1] , this
I added a touchstone build on the matrix project.
The matrix job [1] builds Ant for Windows+Ubuntu for Java 1.5, 1.6 and 1.8.
The whole matrix starts now after a successful run on Java1.5@Ubuntu.
Or do want to get the other builds done in any way?
Jan
[1] https://builds.apache.o
Thanks Jan,
Antoine
On Dec 2, 2014, at 3:57 PM, Jan Matèrne (jhm) wrote:
> I changed the used Java version for the Jenkins job from 1.5 to 1.6 because
> the last few builds failed due a UnsupportedClassVersion error.
>
> https://builds.apache.org/job/Ant_BuildFromPOMs
>
&
I changed the used Java version for the Jenkins job from 1.5 to 1.6 because
the last few builds failed due a UnsupportedClassVersion error.
https://builds.apache.org/job/Ant_BuildFromPOMs
This was easier than searching which of the jars was 1.6+ based ;)
/home/jenkins/tools/java/latest1.6
t;
>
> changed to "ant-1.9.3"
> --> build runs fine
>
> https://builds.apache.org/job/Ivy-tests/jdk=JDK%201.5%20%28latest%29,label=Windows/lastBuild/console
>
> The Ubuntu build is waiting for the next executor.
>
>
> Ant 1.9.4 is not available in the configurati
%20%28latest%29,label=Windows/lastBuild/console
The Ubuntu build is waiting for the next executor.
Ant 1.9.4 is not available in the configuration dialog.
Jan
> -Ursprüngliche Nachricht-
> Von: Apache Jenkins Server [mailto:jenk...@builds.apache.org]
> Gesendet: Montag, 18. A
On 2014-07-25, Stefan Bodewig wrote:
> If Jenkins is set up to create a fresh workspace on each build - which
> I believe it is - it should work.
Two things I needed to do for AntUnit's Jenkins job:
* change the Ant version used from "Standard" to "latest"
* activ
Hi all
I'd like to add git submodules for the common antlib to all remaining
Antlibs, I think all I need to do is to replace the prepare.xml build
file inside common as well as all Antlibs with the version used in the
compress Antlib. If Jenkins is set up to create a fresh workspace on
reff: Re: IvyDE-updatesite - fix for jenkins
>
>
> Le 27 juin 2014 à 22:29, Jan Matèrne a écrit :
>
> > https://builds.apache.org/job/IvyDE-updatesite/ is broken and I think
> > its because it tries to download the ivy.jar from the wrong location.
> > Because I dont have wri
Le 27 juin 2014 à 22:29, Jan Matèrne a écrit :
> https://builds.apache.org/job/IvyDE-updatesite/ is broken and I think its
> because it tries to download the ivy.jar from the wrong location.
> Because I dont have write access to that svn repo, I created a patch.
> Please try ;)
I tried to appli
https://builds.apache.org/job/IvyDE-updatesite/ is broken and I think its
because it tries to download the ivy.jar from the wrong location.
Because I dont have write access to that svn repo, I created a patch.
Please try ;)
cheers
Jan
-
Thanks !
2014-06-18 8:14 GMT+02:00 Jan Matèrne (jhm) :
> All blue now.
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> > Gesendet: Mittwoch, 18. Juni 2014 08:09
> > An: 'Ant Developers List&
All blue now.
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Mittwoch, 18. Juni 2014 08:09
> An: 'Ant Developers List'
> Betreff: AW: Build failed in Jenkins: EasyAnt #175
>
> Changed the configuration
Von: Jean-Louis Boudart [mailto:jeanlouis.boud...@gmail.com]
> Gesendet: Dienstag, 17. Juni 2014 21:38
> An: Ant Developers List
> Betreff: Re: Build failed in Jenkins: EasyAnt #175
>
> Hi,
>
> I added xooki as easyant submodule to handle documentation.
> Unfortunatly jenk
Hi,
I added xooki as easyant submodule to handle documentation.
Unfortunatly jenkins doesn't seems to fetch submodules. I haven't enough
karma there to manage job configuration, could someone with enough karma
check the config to see if there is an option to fetch git submodules ?
201
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
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
Le 5 juin 2014 à 07:12, Jan Matèrne (jhm) a écrit :
> https://builds.apache.org/view/A-D/view/Ant/job/IvyDE/lastBuild/consoleFull
>
> [java] [javac] 650. ERROR in
> /home/jenkins/jenkins-slave/workspace/IvyDE/work/eclipse/plugins/org.apache.
> ivyde.eclipse/src/java/o
https://builds.apache.org/view/A-D/view/Ant/job/IvyDE/lastBuild/consoleFull
[java] [javac] 650. ERROR in
/home/jenkins/jenkins-slave/workspace/IvyDE/work/eclipse/plugins/org.apache.
ivyde.eclipse/src/java/org/apache/ivyde/internal/eclipse/workspaceresolver/W
orkspaceResolver.java (at
The Jenkins job for the first AntLib is running.
If they arent any objections I will clone that for the other AntLibs.
Jan
https://builds.apache.org/job/AntLib-props/
* jdk:
* nodes: ubuntu (= no windows due git problems)
* scm=git
* triggered: after antlib-common (means, if the
pdated the view (add missing ivy-tests)
> https://builds.apache.org/view/A-D/view/Ant/
>
> I deactivated the windows builds until INFRA-7823 is resolved.
> How to deal with the xooki-not-found projects (EasyAnt, IvyDE)?
> a) leave it red
> b) change the build launch command on je
INFRA-7823 is resolved.
How to deal with the xooki-not-found projects (EasyAnt, IvyDE)?
a) leave it red
b) change the build launch command on jenkins (to which new value?)
c) change the buildfile so xooki is not required (not by me ;)
d) b+c
Because I don't know what to do now (expect waitin
it.GitException: Could not init
f:\jenkins\jenkins-slave\workspace\Ant-Build-Matrix@2\jdk\JDK 1.7
(latest)\label\Windows
Caused by: hudson.plugins.git.GitException: Error performing command:
git init f:\jenkins\jenkins-slave\workspace\Ant-Build-Matrix@2\jdk\JDK 1.7
(latest)\label\Windows
On May 27, 2014, at 8:53 AM, Jan Matèrne (jhm) wrote:
> Here is an intermediate result and my opinion on that:
>
>
>
> Open problems
>
> =
>
> Ant-Build-Matrix has problems on Ubuntu and on Windows.
>
> On Windows it seems (to me) that there is no git installed or not on the
>
hudson.plugins.git.GitException: Could not init
f:\jenkins\jenkins-slave\workspace\Ant-Build-Matrix@2\jdk\JDK 1.7
(latest)\label\Windows
Caused by: hudson.plugins.git.GitException: Error performing command:
git init f:\jenkins\jenkins-slave\workspace\Ant-Build-Matrix@2\jdk\JDK 1.7
console
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init
f:\jenkins\jenkins-slave\workspace\Ant-Build-Matrix@2\jdk\JDK 1.7
(latest)\label\Windows
Caused by: hudson.plugins.git.GitException: Error performing command:
git init f:\jenkin
Subject
migration to git : next steps - updating Jenkins jobs
Text
Here is an intermediate result and my opinion on that:
Ant-Build-Matrix has problems on Ubuntu and on Windows.
On Windows it seems (to me) that there is no git installed or not on the
PATH.
--> open an INFRA-Ticket?
On Ubu
Current status:
- Ant-Build-Matrix
repo: git
https://builds.apache.org/job/Ant_BuildFromPOMs/
status: errors on the slaves
- Ant_BuildFromPOMs
repo: git
https://builds.apache.org/job/Ant_BuildFromPOMs/
status: run fine (using locks-and-latches, no archiving)
- Ant_Ni
s List'
> Betreff: AW: migration to git : next steps - Jenkins
>
> I changed the repo urls from svn to git for
> - Ant-Build-Matrix
> - Ant_BuildFromPOMs
> - Ant_Nightly
> - EasyAnt
> - Ivy
> - Ivy-check
> - IvyDE
>
> all with "additional behaviour&quo
I changed the repo urls from svn to git for
- Ant-Build-Matrix
- Ant_BuildFromPOMs
- Ant_Nightly
- EasyAnt
- Ivy
- Ivy-check
- IvyDE
all with "additional behaviour": clean before checkout
and I started the builds.
I'll have to wait for running builds ...
Jan
> -Ursprüngliche Nachricht---
ation filter
!(label.startsWith("Windows") && jdk.startsWith("Open JDK 1.8”))
That does not have a visible effect on the grid, we will soon see whether
jenkins tries to build this combo again.
Antoine
>
>
> Thanks,
>
> Michael
>
>
>
-
The Jenkins master got rebooted shortly after this failure so I don't know
if the Ops were already up to something. Neither Windows slave is currently
active so I can't see if the reboot has recovered the build or not.
Our Windows builds just generally don't seem right:
JDK 1.8 o
Our build is successful but Jenkins is running out of memory processing JUnit
results if I understand correctly.
I wonder whether we should ask Infra to run Jenkins with a larger PermGen space
as the error message suggests or whether there is something else to do on our
end ?
Regards
I updated the Jobs
- deactivated openJDK8 (with a comment)
- let the Matrix build also on jdk-1.8 and openJDK8
- update all Ant Jobs to use Ant 1.9.3
I created an issue for installing Java9 for Jenkins
https://issues.apache.org/jira/browse/INFRA-7558
Haven't changed the build timeout.
We
On Apr 11, 2014, at 2:46 AM, Jan Matèrne (jhm) wrote:
>
> No we have several Java8 installations available on the matrix: Open JDK 1.8
> (Only on ubuntu nodes) + jdk-1.8.0
>
>
>
> Should we
>
> - add these two to the build matrix?
sure
>
> - change the openJDK8 job to use Java9?
+1
>
>
Sounds good,
Antoine
On Apr 11, 2014, at 3:03 AM, Jan Matèrne (jhm) wrote:
> update
> * no Java9 available at Jenkins. So would have to create an JIRA like
> https://issues.apache.org/jira/browse/INFRA-7485
update
* no Java9 available at Jenkins. So would have to create an JIRA like
https://issues.apache.org/jira/browse/INFRA-7485
Jan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h
I have a look at the configuration of the Matrix Job at Apaches Jenkins
instance
https://builds.apache.org/job/Ant-Build-Matrix/configure
We have a special job [1] for openJDK8. I think this was introduced in the
time when Java8 was not released.
No we have several Java8 installations
Thanks, I updated the page.
Jan
> -Ursprüngliche Nachricht-
> Von: Nils Hoffmann [mailto:nils.hoffm...@cebitec.uni-bielefeld.de]
> Gesendet: Freitag, 24. Mai 2013 13:33
> An: Ant Developers List
> Betreff: Website: Broken Jenkins CI Links
>
> Hi Ant Devs,
> I hop
Hi Ant Devs,
I hope that this is the right list to draw your attention to some dead
links on
http://ant.apache.org/nightlies.html
There, obviously all links within the first table, pointing to the
jenkins CI, are broken.
These should be easily fixable, e.g. for the Ant Build Matrix, the
broken
We have the control over the jvm arguments of ant within Jenkins, so we could
probably deal with it ourself.
And actually it doesn't seem to be the Ant launched by Jenkins which is
crashing, it is the boostrapped ant which is. This Jenkins config is launching
ant -f launch-build.xml, whi
On 03/06/2013 07:44 AM, Jesse Glick wrote:
Perhaps the test itself somehow kills the test runner?
More likely an OOME of some kind; asked for help on bui...@apache.org.
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
On 03/05/2013 11:13 PM, Apache Jenkins Server wrote:
[exec] [au:antunit] Build File:
<https://builds.apache.org/job/Ant-Build-Matrix/./jdk=JDK%201.6%20(latest),label=Windows/ws/trunk\src\tests\antunit\taskdefs\exec\apply-test.xml>
[exec] [au:antunit] Tests run: 30, Failu
Le 2 févr. 2013 à 23:12, Maarten Coene a écrit :
> Hi Nicolas,
>
> I think we can remove this job from Jenkins again.
> What do you think?
I think we can safely do as the last build launch was in…. August…
And there was a total of… 1 build done…
I have missed something when I
Hi Nicolas,
I think we can remove this job from Jenkins again.
What do you think?
Maarten
From: Nicolas Lalevée
To: Ant Developers List
Sent: Wednesday, August 22, 2012 10:56 AM
Subject: Re: Ivy 2.3.x tested on Jenkins
The Ivy-tests job now run on both
> Maarten
>
>
>
>
> From: Nicolas Lalevée
> To: Ant Developers List
> Sent: Monday, August 20, 2012 5:20 PM
> Subject: Ivy 2.3.x tested on Jenkins
>
> Since the trunk is moving a little from the 2.3.x branch, I have setup a
> build of the Ivy test suite of the 2.3.
Thanks Nicolas :-)
I also think a build matrix for Ivy would be a good idea...
Maarten
From: Nicolas Lalevée
To: Ant Developers List
Sent: Monday, August 20, 2012 5:20 PM
Subject: Ivy 2.3.x tested on Jenkins
Since the trunk is moving a little from the 2.3
Since the trunk is moving a little from the 2.3.x branch, I have setup a build
of the Ivy test suite of the 2.3.x branch:
https://builds.apache.org/job/Ivy-2.3-tests/
Also, I have seen Maarten struggle with Unix path just like I do with Windows
paths :)
I think it will be interesting to do a "bu
Looks like Ant-Build-Matrix is finally fixed! I have reenabled mail sent to
notificati...@ant.apache.org so we can track regressions.
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev
Le 9 avr. 2012 à 07:35, Stefan Bodewig a écrit :
> Hi,
>
> by now I've managed to reduce the number of failing tests to 0 on two of
> the six build configurations. What remains:
>
> * a failure that only happens on Java5 machines WRT a closed ZIP. I'll
> re-investigate what is going on here
Hi,
by now I've managed to reduce the number of failing tests to 0 on two of
the six build configurations. What remains:
* a failure that only happens on Java5 machines WRT a closed ZIP. I'll
re-investigate what is going on here tomorrow
* some stange host-name resolution issue with the Ubun
Le 18 mars 2012 à 07:40, Stefan Bodewig a écrit :
> On 2012-03-16, Nicolas Lalevée wrote:
>
>> Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
>
>>> On 2012-03-09, Nicolas Lalevée wrote:
>
>>>> As a quick fix I guess we can add in the command line laun
On 2012-03-16, Nicolas Lalevée wrote:
> Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
>> On 2012-03-09, Nicolas Lalevée wrote:
>>> As a quick fix I guess we can add in the command line launched by
>>> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
>> Have
Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
> On 2012-03-09, Nicolas Lalevée wrote:
>
>> As a quick fix I guess we can add in the command line launched by
>> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
>
> Have you changed the configuration to contain that? If
On 2012-03-09, Nicolas Lalevée wrote:
> As a quick fix I guess we can add in the command line launched by
> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
Have you changed the configuration to contain that? If so, it doesn't
look to have had any effe
On 03/09/2012 04:16 AM, Nicolas Lalevée wrote:
As a quick fix I guess we can add in the command line launched by Jenkins a
-Djava.io.tmpdir=$WORKSPACE/tmpdir
I guess that would work for the AntUnit tests, so try that. For JUnit tests it
would probably have no effect since these run in a
As a quick fix I guess we can add in the command line launched by Jenkins a
-Djava.io.tmpdir=$WORKSPACE/tmpdir
Should I do that or we want to get rid of java.io.tmpdir ?
Nicolas
Le 9 mars 2012 à 05:57, Stefan Bodewig a écrit :
> On 2012-03-09, Jesse Glick wrote:
>
>> On 03/08/2
On 2012-03-09, Jesse Glick wrote:
> On 03/08/2012 12:04 AM, Stefan Bodewig wrote:
>> do we have to do anything special to provide the Jenkins build with a
>> ${java.to.tmpdir} that it actually is allowed to write to?
> Using ${java.io.tmpdir} from tests is a bit dangerous anywa
On 03/08/2012 12:04 AM, Stefan Bodewig wrote:
do we have to do anything special to provide the Jenkins build with a
${java.to.tmpdir} that it actually is allowed to write to?
Using ${java.io.tmpdir} from tests is a bit dangerous anyway; the files may rarely or never get cleaned up, you need to
On 2012-03-07, Jesse Glick wrote:
> On 03/06/2012 12:53 PM, Nicolas Lalevée wrote:
>> [AntUnit] results were not aggregated by Jenkins. I have fixed it.
> Confirmed; #462 shows tons of AntUnit failures. Whoever wrote these
> tests and is still around, consider reviewing them.
I h
On 03/06/2012 06:21 PM, Jesse Glick wrote:
#462 shows tons of AntUnit failures
BTW I disabled email notifications as it looks like we are a long way from
fixing all of these tests.
-
To unsubscribe, e-mail: dev-unsubscr...@
On 03/06/2012 12:53 PM, Nicolas Lalevée wrote:
[AntUnit] results were not aggregated by Jenkins. I have fixed it.
Confirmed; #462 shows tons of AntUnit failures. Whoever wrote these tests and is still around, consider reviewing them. (I do not think it is safe to do much of anything
in trunk
> stable build (#461)? Also the workspace is missing. Note that #461's console
> reports all six configs being run and ending with SUCCESS.
This is indeed weird, probably a bug...
> 2. I do not see any test results from AntUnit - do these get run but just not
> reported?
Yep, th
On 03/05/2012 01:33 PM, Jesse Glick wrote:
I am looking into some of the test failures.
I think I have fixed most of the failures, though there are still some things
that seem to fail at random, especially on Windows.
Two points of confusion:
1. All the JDK 1.5 and 1.6 history - including te
On 03/03/2012 12:51 PM, Nicolas Lalevée wrote:
So we would have Ant_Nightly which builds the distrib of Ant and gather
findbugs warnings, java warnings and TODO/FIXMEs, and we would have the tests
run by Ant-Build-Matrix.
Looks like an improvement - thanks for setting this up. I am looking in
On 2012-03-03, Nicolas Lalevée wrote:
> Le 3 mars 2012 à 06:15, Stefan Bodewig a écrit :
>> Hi all,
>> before we can start using Java5 stuff in trunk, we need to disable the
>> JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
>> isn't one al
Le 3 mars 2012 à 06:15, Stefan Bodewig a écrit :
> Hi all,
>
> before we can start using Java5 stuff in trunk, we need to disable the
> JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
> isn't one already). It may be worthwhile to have a 1.4 build for t
Hi all,
before we can start using Java5 stuff in trunk, we need to disable the
JDK 1.4 build in Jenkins and replace it with a Java5 build (if there
isn't one already). It may be worthwhile to have a 1.4 build for the
1.8.x branch if we ever intend to create 1.8.4, but this can wait.
Can an
sue is more about having a jvm 1.4
available.
Nicolas
>
> Matt
>
> On Tue, Jun 7, 2011 at 2:42 PM, Apache Jenkins Server
> wrote:
>> See <https://builds.apache.org/job/Ivy-tests/49/changes>
>>
>> Changes:
>>
>> [mbenson] [IVY-1301] Ivy
;) Me learning why builds are restricted to Ubuntu slaves; seemingly
they're the ones that are properly configured!
Matt
On Tue, Jun 7, 2011 at 2:42 PM, Apache Jenkins Server
wrote:
> See <https://builds.apache.org/job/Ivy-tests/49/changes>
>
> Changes:
>
> [mbenso
What was the reason for restricting the Ivy builds to this slave?
Matt
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Matt,
the junit tests were running in another separate project:
https://builds.apache.org/job/Ivy-tests/
Maarten
From: Matt Benson
To: Ant Developers List
Sent: Monday, June 6, 2011 5:28 PM
Subject: Re: Ivy Jenkins build
FYI I experimented with running
FYI I experimented with running these targets; build completed
successfully in 3.x minutes. I'm not going to revert my change unless
someone presents a good reason to do so.
Matt
On Mon, Jun 6, 2011 at 10:18 AM, Matt Benson wrote:
> Why do we only do a 'clean jar'? Shouldn't we be running unit
Why do we only do a 'clean jar'? Shouldn't we be running unit tests
at least? Isn't that kind of the point of CI? Perhaps 'clean
coverage-report'?
Matt
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional co
101 - 185 of 185 matches
Mail list logo
