[libvirt PATCH 0/2] ci: Enable Cirrus CI integration

Andrea Bolognani abologna at redhat.com
Mon Jun 8 17:07:46 UTC 2020

On Mon, 2020-06-08 at 17:34 +0100, Daniel P. Berrangé wrote:
> On Mon, Jun 08, 2020 at 05:42:31PM +0200, Andrea Bolognani wrote:
> > 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
> Ideally the actual build output from Cirrus CI would be pulled into
> the build output of the GitLab CI job. That way email notifications
> from failed builds will include the actual compile failure details.
> This also avoids having to cut+paste non-clickable links to the
> Cirrus CI job.

I agree that this would be desirable.

Earlier today, while reviewing the code for cirrus-run, I found a
reference to a CIRRUS_LOG_FILE environment variable that should
allow us to do just that, and was intending to try it out. If that
doesn't work out, we should still be able to fetch the full job
output from Cirrus CI after the fact.

Andrea Bolognani / Red Hat / Virtualization

More information about the libvir-list mailing list