Re: Jenkins build is back to normal : IvyDE-updatesite #787

[Gintautas Grigelionis]

Great! Still, the build still uses the pretty old Eclipse 3.7.1, and AFAICS
the newer releases do not include drops, so some other dependency
resolution mechanism will be necessary should for example we start
discussing GEF 4+.

2017-05-17 20:48 GMT+02:00 Nicolas Lalevée :

> The build was broken because Ant was requiring a JDK 8. So I have setup
> the build to use the latest JDK 8.
>
> > Le 17 mai 2017 à 20:31, Apache Jenkins Server 
> a écrit :
> >
> > See  >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Jenkins build is back to normal : IvyDE-updatesite #787

[Nicolas Lalevée]

The build was broken because Ant was requiring a JDK 8. So I have setup the 
build to use the latest JDK 8.

> Le 17 mai 2017 à 20:31, Apache Jenkins Server  a 
> écrit :
> 
> See 
> 


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

[GitHub] ant-ivy pull request #16: Fix download URL for findbugs task

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ant-ivy/pull/16


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Ivy - Buildjobs/PreCommit

[J Pai]

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.org/view/A/view/Ant/job/Ivy-check 

But it seems broken too due to some broken download link. The init-findbug task 
needs to be fixed.


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

[GitHub] ant-ivy pull request #16: Fix download URL for findbugs task

[jaikiran]

GitHub user jaikiran opened a pull request:

https://github.com/apache/ant-ivy/pull/16

Fix download URL for findbugs task

The commit here fixes the download URL used in the `init-findbugs` task, 
that has been failing[1] for a while due to reference to an URL that no longer 
works.

The goal of this PR is to just get the download working fine and it's not 
an intention at this point to upgrade a more recent compatible version of 
findbugs.


[1] https://builds.apache.org/view/A/view/Ant/job/Ivy-check/343/console

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaikiran/ant-ivy findbugs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #16


commit 6390a33f40dd9ef478de06da17b929143dac1392
Author: Jaikiran Pai 
Date:   2017-05-17T15:38:05Z

Fix download URL for findbugs task




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: [jira] [Resolved] (IVY-1520) Have makepom task take description from ivy-module > info > description element

[Nicolas Lalevée]

FYI, the things fixed in the master in git are marked in jira « master » as « 
fix version », so that we can just rename it when the release is done, wether 
we do a 2.5.0 or 2.4.x.
Here we’ll indeed do a 2.5.0, but since others jira are already marked as on « 
master », I changed this one.

Nicolas

> Le 17 mai 2017 à 14:36, Jan Matèrne (JIRA)  a écrit :
> 
> 
> [ 
> https://issues.apache.org/jira/browse/IVY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Jan Matèrne resolved IVY-1520.
> --
>   Resolution: Fixed
>Fix Version/s: 2.5.0-RC1
> 
>> Have makepom task take description from ivy-module > info > description 
>> element
>> ---
>> 
>>Key: IVY-1520
>>URL: https://issues.apache.org/jira/browse/IVY-1520
>>Project: Ivy
>> Issue Type: Improvement
>> Components: Ant
>>   Affects Versions: 2.4.0
>>   Reporter: Eric Milles
>>   Priority: Minor
>>Fix For: 2.5.0-RC1
>> 
>> 
>> I've been exploring the Ant ivy:makepom task in more detail and found that I 
>> can transfer the module, organisation and homepage from the original Ivy 
>> file but not the description.  The docs for makepom say that I can set 
>> property ivy.pom.description or use a description element.  But using either 
>> of these does not present me with a straightforward means of transferring 
>> the description from the resolved Ivy file.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)


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

Re: Ivy - Buildjobs/PreCommit

[Nicolas Lalevée]

Seems to be a classpath issue where two ivy.jar are loaded. Considering the 
full console log, probably due to init-ivy called twice, a consequence of Ant 
not computing one unified tree of tasks to call, but a list of trees of the 
tasks on the command line.

The build dedicated to check the style of Ivy is just calling: ant findbugs 
checkstyle-internal
https://builds.apache.org/view/A/view/Ant/job/Ivy-check 

But it seems broken too due to some broken download link. The init-findbug task 
needs to be fixed.

Nicolas

> Le 17 mai 2017 à 14:11, Jan Matèrne (jhm)  a écrit :
> 
> My last test result:
> The Jenkins job could not load Findbugs. So I have deactivated that for the 
> moment.
> 
> https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/6/console
> ant-1.9.9> ant clean jar sources checkstyle-internal coverage-report 
>  resolve:
>  BUILD FAILED
>  /.../build.xml:184: java.lang.ClassCastException: 
> org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor cannot be cast 
> to org.apache.ivy.core.module.descriptor.ModuleDescriptor
>   at 
> org.apache.ivy.ant.IvyPostResolveTask.getConfsToResolve(IvyPostResolveTask.java:233)
>   at 
> org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:219)
>   at 
> org.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=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 - Buildjobs/PreCommit
>> 
>> 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) 
>> 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.forums2...@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  wrote:
>>> 
>>> 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.
 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-unsubscr...@ant.apache.org For additional
>>> commands, e-mail: dev-h...@ant.apache.org
>>> 
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: 

AW: Ivy - Buildjobs/PreCommit

[jhm]

My last test result:
The Jenkins job could not load Findbugs. So I have deactivated that for the 
moment.

https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/6/console
ant-1.9.9> ant clean jar sources checkstyle-internal coverage-report 
  resolve:
  BUILD FAILED
  /.../build.xml:184: java.lang.ClassCastException: 
org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor cannot be cast to 
org.apache.ivy.core.module.descriptor.ModuleDescriptor
at 
org.apache.ivy.ant.IvyPostResolveTask.getConfsToResolve(IvyPostResolveTask.java:233)
at 
org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:219)
at 
org.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=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 - Buildjobs/PreCommit
> 
> 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) 
> 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.forums2...@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  wrote:
> >
> > 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.
> >> 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-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



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

[GitHub] ant-ivy pull request #15: Create just-test-github-integration

[janmaterne]

GitHub user janmaterne opened a pull request:

https://github.com/apache/ant-ivy/pull/15

Create just-test-github-integration



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivy patch-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 648235b057d3ef7a51d0d711b7cd2e9493aeb572
Author: janmaterne 
Date:   2017-05-17T11:58:51Z

Create just-test-github-integration




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] ant-ivy pull request #14: Create just-test-github-integration

[janmaterne]

Github user janmaterne closed the pull request at:

https://github.com/apache/ant-ivy/pull/14


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Ivy - Buildjobs/PreCommit

[J Pai]

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)  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.forums2...@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  wrote:
> 
> 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.
>> 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-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

[GitHub] ant-ivy pull request #14: Create just-test-github-integration

[janmaterne]

GitHub user janmaterne opened a pull request:

https://github.com/apache/ant-ivy/pull/14

Create just-test-github-integration



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivy patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14


commit 425ac7e2c3130aa4efdf1a42078b9be329d4600d
Author: janmaterne 
Date:   2017-05-17T10:37:55Z

Create just-test-github-integration




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

AW: Ivy - Buildjobs/PreCommit

[jhm]

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.forums2...@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  wrote:
> 
> 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.
> > 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-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

[GitHub] ant-ivy issue #13: Dummy PR - Do not merge

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/13
  
retest this please



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Ivy - Buildjobs/PreCommit

[J Pai]

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  wrote:

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.
> 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-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

[GitHub] ant-ivy pull request #13: Dummy PR - Do not merge

[jaikiran]

GitHub user jaikiran opened a pull request:

https://github.com/apache/ant-ivy/pull/13

 Dummy PR - Do not merge

This is just a dummy PR to test the PR integration with Jenkins jobs on 
Apache infra

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaikiran/ant-ivy dummy

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit cb81e0ac5db44837ad7621e32fae00c48e4e283d
Author: Jaikiran Pai 
Date:   2017-05-17T08:43:34Z

Dummy commit




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Ivy - Buildjobs/PreCommit

[J Pai]

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.
> 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-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

AW: Ivy - Buildjobs/PreCommit

[jhm]

> 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-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Ivy - Buildjobs/PreCommit

[Jan Matèrne]

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 ...


Jan




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