For reference, the Travis CI usage was also discussed in INFRA-18533.
Since July 8th the Flink project is no longer running PR builds on ASF
resources.Instead we mirror pull requests into an external repository
and run these builds in a sponsored Travis account. If anyone is
interested, check out the above JIRA.
The reduction in ASF resource usage is less than expected because we're
currently in the process of creating a new release, which usually
doubles our CI usage temporarily (since many fixes are merged to master
and a release branch).
Nevertheless, looking at the resource usage since then (via
https://kibble.dev), we are now in 4th place, behind incubator-druid.
In the future we also plan to migrate our push/cron builds to the
external repository, but I can't provide an ETA for this.
On 2019/07/19 03:51:08, David Nalley <da...@gnsa.us> wrote:
> On Tue, Jul 16, 2019 at 5:37 PM Greg Stein <gst...@gmail.com> wrote:
> >
> > Ray,
> >
> > Thanks for the offer of 50k minutes/project. That will definitely
work for
> > most projects.
> >
> > While we don't have precise measurements, some projects used *way* more
> > than that within Travis last month:
> >
> > flink: 350k minutes
> > arrow: 260k minutes
> > cloudstack: 190k minutes
> > incubator-druid: 96k
> > airflow: 77k
> > ... others: less than 50k
> >
> > I don't know what would be needed from Infra, to enable the use of
Gitlab
> > CI for our projects. ??
> >
> > Thanks,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>
> It's also worth noting that those numbers are likely constrained by
> our capacity. IIRC Humbedooh said we'd need something close to double
> our currently capacity to satiate the backlog of build requests that
> we had.
>
> Our current travis load should be something like 1.72MM minutes per
month.
>
> --David
>
