groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Bayer <andrew.ba...@gmail.com>
Subject Re: Buildserver Github Pull Request Integration (Enabling Travis CI)
Date Mon, 19 Oct 2015 18:34:02 GMT
Fwiw, we can build and update pull requests on builds.apache.org as well.
On Oct 19, 2015 20:30, "Pascal Schumacher" <pascalschumacher@gmx.net> wrote:

> Hello everybody,
>
> according to the web TeamCity requires write access to the repo to update
> pull requests with test results. As this is not possible to with the Apache
> Github mirror, I suggest we use Travis CI to test pull request.
>
> Apache has a subscription for Travis CI
> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
> and according to
> http://de.slideshare.net/jukka/apache-development-with-github-and-travis-ci
> we only need to create a infrastructure ticket to enable the Travis Webhook
> for the mirror.
>
> If there are no objections I will add a ".travis.yml" file and create the
> infrastructure ticket.
>
> -Pascal
>
>
>
>
>
> Am 13.09.2015 um 10:46 schrieb Pascal Schumacher:
>
>> Hello everybody,
>>
>> before moving to Apache TeamCity updated the pull request after running
>> the tests, e.g.:
>>
>> https://github.com/groovy/groovy-core/pull/648
>>
>> Is this no possible with the Apache Github clone?
>>
>> If it's not possible with TeamCity maybe we should add Travis to test
>> pull request (as Thibault suggested in
>> https://github.com/apache/incubator-groovy/pull/112), because Travis
>> it's possible, e.g.:
>>
>> https://github.com/apache/commons-lang/pull/107
>>
>> -Pascal
>>
>>
>

Mime
View raw message