This is an alternative approach to the one proposed by Erik[1].
Advantages of this approach:
* we don't have to build and maintain our own FreeBSD runners;
* we make it possible, after some straightforward one-time setup,
for any contributor to have their branches build on FreeBSD and
macOS, again without having to build and maintain their own
runners;
* we reduce the number of services external of GitLab that we
depend on by having FreeBSD and macOS build happen on the same
platform instead of separate ones.
Drawbacks of this approach:
* requires signing up for yet another online service.
To see this in action, check out the
https://gitlab.com/abologna/libvirt/-/pipelines/153963978
pipeline, and in particular the
https://gitlab.com/abologna/libvirt/-/jobs/585678408
https://gitlab.com/abologna/libvirt/-/jobs/585678413
jobs.
libvirt-ci merge request:
https://gitlab.com/libvirt/libvirt-ci/-/merge_requests/16
[1] https://www.redhat.com/archives/libvir-list/2020-June/msg00188.html
Andrea Bolognani (2):
ci: Enable Cirrus CI integration
ci: Remove Travis CI
.gitlab-ci.yml | 36 ++++++++++++++++++
.travis.yml | 58 -----------------------------
ci/README.rst | 59 ++++++++++++++++++++++++++++++
ci/cirrus/freebsd-11.yml.j2 | 73 +++++++++++++++++++++++++++++++++++++
ci/cirrus/freebsd-12.yml.j2 | 73 +++++++++++++++++++++++++++++++++++++
ci/cirrus/macos-1015.yml.j2 | 38 +++++++++++++++++++
6 files changed, 279 insertions(+), 58 deletions(-)
delete mode 100644 .travis.yml
create mode 100644 ci/README.rst
create mode 100644 ci/cirrus/freebsd-11.yml.j2
create mode 100644 ci/cirrus/freebsd-12.yml.j2
create mode 100644 ci/cirrus/macos-1015.yml.j2
--
2.25.4
