[Mesa-dev] [PATCH v2 0/5] Use GitLab CI to build Mesa
daniel at fooishbar.org
Fri Sep 28 10:34:04 UTC 2018
On Fri, 21 Sep 2018 at 20:59, Daniel Stone <daniel at fooishbar.org> wrote:
> On Wed, 29 Aug 2018 at 11:13, Juan A. Suarez Romero <jasuarez at igalia.com> wrote:
> > This is a first part, version 2, of a more complete proposal to use GitLab CI to
> > build and test Mesa. This first part just adds the required pieces to build
> > Mesa, using the different supported tools (meson, autotools, and scons).
> > A second part, to be sent in the future, will use the results of the former to
> > run different tests and verify everything works fine.
> > An example of the pipeline that will result from this patchset can be seen at
> > https://gitlab.freedesktop.org/jasuarez/mesa/pipelines/3070.
> > I hope I can explain here all the rationale behind this proposal. Any question
> > is welcomed.
> I still have an open NAK since this would DoS our existing fd.o CI
> runner infrastructure; GitLab itself is fine, but subjecting our
> elderly build machine with a flaky network on the wrong continent to
> this would be too much.
> I'm pretty sure that I'll be able to stand up two sets of runners -
> one still based in the UK, but on modern and dedicated machines with
> better network; another on a US-based cloud provider, matching our
> us-east GitLab master location - before XDC starts, so during XDC we
> could get those as dedicated runners for a fork of the Mesa project
> and try to gather some stats and profiles on how they actually
> Hopefully if it goes well then we should be able to switch them on
> almost immediately.
Unfortunately we're still externally stalled on this. I'd suggest that
we give Juan owner access to the Mesa project in GitLab, so he can
connect the existing Igalia runners to our project. These runners
already do the execution for the gitlab.com project, so should be more
than enough to run ours until we can get the external runners.
Anyone object, agree, other?
More information about the mesa-dev