Long queue time on travis-ci

[Jia Yu <ji...@gmail.com>]

Hi Felix,

I notice that recently, the Travis-CI auto-build on our PRs and commits
seem to have a very long queue time (
https://travis-ci.org/github/apache/incubator-sedona/builds/742278311)

Is this because we are under Apache organization and there are hundreds of
builds going on? Or is this because the build is based on a non-master
branch? If we push the commit to the master branch, will the build be
faster?

Thanks,
Jia

Re: Long queue time on travis-ci

[Jia Yu <ji...@gmail.com>]

Hi all,

I have moved the CI to GitHub action. It turns out that GitHub action is
way better than Travis-CI. Please see my PR:
https://github.com/apache/incubator-sedona/pull/491

However, it looks like GitHub action has a limitation:
https://github.com/pricing

We should probably only limit the Actions to the master branch. Any
suggestions?

Jia

On Sun, Nov 8, 2020 at 1:28 PM Felix Cheung <fe...@apache.org> wrote:

> Hello,
>
> There has been, in the past, incidents where the shared Travis resource is
> exhausted.
>
> It might help if you restrict to build one branch (like main) only.
>
> Some projects have acquired corporate sponsorship for a separate Travis
> instance.
>
> Some has moved to another system, like GitHub Action (eg superset or
> airflow)
>
> https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub
> (I am not certain if there is any fee involved)
>
> ASF has no policy against using other CI or test system.
>
>
> On Sun, Nov 8, 2020 at 11:23 AM Jia Yu <ji...@gmail.com> wrote:
>
>> Hi Felix,
>>
>> I notice that recently, the Travis-CI auto-build on our PRs and commits
>> seem to have a very long queue time (
>> https://travis-ci.org/github/apache/incubator-sedona/builds/742278311)
>>
>> Is this because we are under Apache organization and there are hundreds
>> of builds going on? Or is this because the build is based on a non-master
>> branch? If we push the commit to the master branch, will the build be
>> faster?
>>
>> Thanks,
>> Jia
>>
>

Re: Long queue time on travis-ci

[Felix Cheung <fe...@apache.org>]

Hello,

There has been, in the past, incidents where the shared Travis resource is
exhausted.

It might help if you restrict to build one branch (like main) only.

Some projects have acquired corporate sponsorship for a separate Travis
instance.

Some has moved to another system, like GitHub Action (eg superset or
airflow)
https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub
(I am not certain if there is any fee involved)

ASF has no policy against using other CI or test system.


On Sun, Nov 8, 2020 at 11:23 AM Jia Yu <ji...@gmail.com> wrote:

> Hi Felix,
>
> I notice that recently, the Travis-CI auto-build on our PRs and commits
> seem to have a very long queue time (
> https://travis-ci.org/github/apache/incubator-sedona/builds/742278311)
>
> Is this because we are under Apache organization and there are hundreds of
> builds going on? Or is this because the build is based on a non-master
> branch? If we push the commit to the master branch, will the build be
> faster?
>
> Thanks,
> Jia
>