On Wed, Oct 14, 2020 at 3:41 AM Daniel P. Berrangé
<berrange(a)redhat.com>
wrote:
> On Wed, Oct 14, 2020 at 10:37:26AM +0100, Richard W.M. Jones wrote:
> > On Tue, Oct 13, 2020 at 03:21:35PM -0600, alan somers wrote:
> > > Would libguestfs be willing to enable CI for the nbdkit project?
> It's very
> > > easy to set up, at least for the Rust portion. I'm comfortable with
> both
> > > Cirrus CI and Github's native CI. I can get it started if you agree
> to do it.
> >
> > Sure.
> >
> > Be aware we may move to gitlab (same as libvirt) at some point soon.
> > Libvirt went with gitlab's CI:
> >
https://gitlab.com/libvirt/libvirt/-/pipelines
>
> If you want to follow libvirt's approach, then you can also use our
> libvirt-ci tools for creating the container dockerfiles for all the
> distros, which simplifies keeping everything in sync.
>
> Regards,
> Daniel
> --
> |:
https://berrange.com -o-
>
https://www.flickr.com/photos/dberrange :|
> |:
https://libvirt.org -o-
>
https://fstop138.berrange.com :|
> |:
https://entangle-photo.org -o-
>
https://www.instagram.com/dberrange :|
>
Until and unless you move to Gitlab, I suggest Cirrus-CI. It's easy to
configure; so there's little lost effort if we abandon it. I've already
got the configuration ready to go. But I don't have permission to enable
the application on the repository. Could a repo owner please follow the
steps at
https://cirrus-ci.org/guide/quick-start/ ? Stop when you get to
"post-installation", and I'll take over.
-Alan
Ping. Could somebody please enable Cirrus- CI? This is blocking me from
publishing the crate. Or, if you really really really don't want to have
any CI, I can just create a new repo for the Rust plugin. That way you
wouldn't need to change your workflow.
-Alan