ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From J Pai <jai.forums2...@gmail.com>
Subject Re: Ivy - Buildjobs/PreCommit
Date Wed, 17 May 2017 11:18:29 GMT
Updated the same PR and that triggered this job https://builds.apache.org/job/Ivy-GithubPR/3/.
It failed to build due to a host not being resolvable. This job ran on node called H15 https://builds.apache.org/computer/H15/
whereas the first job which had succeeded had run on https://builds.apache.org/computer/qnode3/.
Maybe all nodes are not equal and perhaps this job needs to be assigned/categorized to certain
node groups?

-Jaikiran
On 17-May-2017, at 4:03 PM, Jan Matèrne (jhm) <apache@materne.de> wrote:

Thanks, I changed the job to run:

ant clean jar sources findbugs checkstyle-internal coverage-report
ant -f build-release.xml -Drat.failOnError=false rat

Please try again ;)


Jan


> -----Ursprüngliche Nachricht-----
> Von: J Pai [mailto:jai.forums2013@gmail.com]
> Gesendet: Mittwoch, 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 indeed trigger
> the Jenkins job https://builds.apache.org/view/A/view/Ant/job/Ivy-
> GithubPR/1/ automagically :) I’m guessing this job isn’t running any
> tests right now (given how quickly it finished)?
> 
> This is good start to getting this working. Thanks for getting this
> setup :)
> 
> -Jaikiran
> 
> 
> On 17-May-2017, at 2:07 PM, J Pai <jai.forums2013@gmail.com> wrote:
> 
> Doesn’t look like it got triggered in Jenkins.
> 
> -Jaikiran
> On 17-May-2017, at 1:49 PM, Jan Matèrne (jhm) <apache@materne.de>
> 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.
>> For me this works like that:
>> 1. The PreCommit-Admin job checks regularly on for new patches in
> Jira.
>> 2. It invokes the "PreCommit-{JiraProject}" job mit Jira-ID and
>> file-ID as argument.
>> 3. The job does the rest.
>> 
>> That means the job itself has to apply the patchfile - and of course
>> run the build.
>> 
>> On the other hand I found a blog post from infra
>> https://blogs.apache.org/infra/entry/github_pull_request_builds_now
>> and set up an according job
>> https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/
>> This job uses the Github integration by Cloudbees Enterprise plugin.
>> So next step for test would be a new/updated PR ...
> 
> I've created a small PR https://github.com/janmaterne/ant-ivy/pull/1.
> Now ... wait ;)
> 
> Jan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message