On Tue, 2020-03-10 at 10:09 +0000, Daniel P. Berrangé wrote:
> With GitLab CI aiming to replace Jenkins and Travis for CI purposes, we
> need to expand the coverage to include native builds. This patch adds
> all the jobs currently run in Travis. Compared to Jenkins we obviously
> miss the FreeBSD jobs, but also Debian 10 and Fedora 30, but we gain the
> Ubuntu 1804 job as a substitute for Debian.
Once again, two questions:
* why are we replicating the jobs that already exist in Travis
CI? I get it that we eventually want to move everything over to
GitLab CI, but for the time being it looks like we're not really
gaining anything from culling jobs - we're just significantly
reducing our test coverage;
* what's the endgame here? Are we going to rely solely on the
runners that GitLab provides for free, or are we going to plug
our own runners into the infrastructure? Because the former
would severely limit our test coverage, and bring it down to a
much, much worse state than what we currently have.
--
Andrea Bolognani / Red Hat / Virtualization
