I changed the Ivy build jobs to use Java7 instead of Java6.
Jan
mit being merged into the asf repo.
Nicolas
>
>
> Jan
>
>> -Ursprüngliche Nachricht-
>> Von: J Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Montag, 22. Mai 2017 14:45
>> An: Ant Developers List
>> Betreff: Re: Ivy - Buildjobs/PreCommi
x27;t. So we should define only 2-4
most interesting configs like
- Java7@Unix
- Java7@Windows
- Java8@Unix
Jan
> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 22. Mai 2017 14:45
> An: Ant Developers List
> Betreff: Re: Ivy -
It looks like there might be some issue with the matrix job(s)
https://builds.apache.org/job/Ivy-GithubPR-Matrix/2/console
From what I understand of that log, it seems like the parent matrix job (the
one above) is correctly checking out the commit from the submitted PR:
> Checking out Revision
> > On a related note, while we are at this - does Apache infra allow the
> jobs to be run against Windows OS Jenkins agents as well? There are a
> few issues specifically reported against Windows OS and having the job
> run against linux and Windows OS should give a decent coverage for the
> upstr
I'll try setting up the PreCommit-Job as Matrix job with Linux/Window.
Jan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
> Le 20 mai 2017 à 11:18, Nicolas Lalevée a écrit :
>
>
>> Le 20 mai 2017 à 04:45, J Pai a écrit :
>>
>> This pre-commit job is now almost functional. It gets triggered whenever
>> there’s a PR and runs the build and tests and reports back if there are any
>> failures.
>>
>> However, the o
esolveTask.prepareAndCheck(IvyPostResolveTask.java:179)
>>> at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:88)
>>> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:272)
>>>
>>> ant-1.9.9> ant -f build-release.xml -Drat.failOnError=f
.ant.IvyTask.execute(IvyTask.java:272)
>>
>> ant-1.9.9> ant -f build-release.xml -Drat.failOnError=false rat
>> not run due to prior problems
>>
>>
>> Some ideas?
>>
>>
>> Jan
>>
>>
>>> -Ursprüngliche Nachricht-
rg.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:179)
>> at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:88)
>> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:272)
>>
>> ant-1.9.9> ant -f build-release.xml -Drat.failOnError=fal
>
> Some ideas?
>
>
> Jan
>
>
>> -Ursprüngliche Nachricht-
>> Von: J Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Mittwoch, 17. Mai 2017 13:18
>> An: Ant Developers List
>> Betreff: Re: Ivy - Buildjobs/PreCommit
>>
&g
I just submitted a PR https://github.com/apache/ant-ivy/pull/16 which I think
should fix the init-findbug task.
-Jaikiran
On 17-May-2017, at 6:59 PM, Nicolas Lalevée wrote:
The build dedicated to check the style of Ivy is just calling: ant findbugs
checkstyle-internal
https://builds.apache.or
>> -Ursprüngliche Nachricht-
>> Von: J Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Mittwoch, 17. Mai 2017 13:18
>> An: Ant Developers List
>> Betreff: Re: Ivy - Buildjobs/PreCommit
>>
>> Updated the same PR and that triggered this jo
9.9> ant -f build-release.xml -Drat.failOnError=false rat
not run due to prior problems
Some ideas?
Jan
> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Mittwoch, 17. Mai 2017 13:18
> An: Ant Developers List
> Betreff: Re: Ivy
-report
ant -f build-release.xml -Drat.failOnError=false rat
Please try again ;)
Jan
> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Mittwoch, 17. Mai 2017 10:53
> An: Ant Developers List
> Betreff: Re: Ivy - Buildjobs/PreCommit
>
>
, 17. Mai 2017 10:53
> An: Ant Developers List
> Betreff: Re: Ivy - Buildjobs/PreCommit
>
> It turns out the PR you submitted was to your personal repo instead of
> the apache repo. I just submitted a dummy PR to apache repo
> https://github.com/apache/ant-ivy/pull/13 and that did i
It turns out the PR you submitted was to your personal repo instead of the
apache repo. I just submitted a dummy PR to apache repo
https://github.com/apache/ant-ivy/pull/13 and that did indeed trigger the
Jenkins job https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/1/
automagically :)
Doesn’t look like it got triggered in Jenkins.
-Jaikiran
On 17-May-2017, at 1:49 PM, Jan Matèrne (jhm) wrote:
> I read the wiki page https://wiki.apache.org/general/PreCommitBuilds,
> the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and
> had a look at some other PreCommit-jobs.
> I read the wiki page https://wiki.apache.org/general/PreCommitBuilds,
> the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and
> had a look at some other PreCommit-jobs.
> For me this works like that:
> 1. The PreCommit-Admin job checks regularly on for new patches in Jira.
> 2. It
I read the wiki page https://wiki.apache.org/general/PreCommitBuilds, the
Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and had a look
at some other PreCommit-jobs.
For me this works like that:
1. The PreCommit-Admin job checks regularly on for new patches in Jira.
2. It invokes the
20 matches
Mail list logo
