ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From J Pai <>
Subject Re: Ivy - Buildjobs/PreCommit
Date Wed, 17 May 2017 08:52:46 GMT
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 and that did
indeed trigger the Jenkins job
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 :)


On 17-May-2017, at 2:07 PM, J Pai <> wrote:

Doesn’t look like it got triggered in Jenkins.

On 17-May-2017, at 1:49 PM, Jan Matèrne (jhm) <> wrote:

> I read the wiki page,
> the Kafka issue 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
> and
> set up an according job
> 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
Now ... wait ;)


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message