e4327557a4
Right now the jobs have no rules so they will always be created in a pipeline. If the user's fork has no runner configured, then the jobs will never be able to execute and the pipeline will not finish. Even on upstream, there might be times the runner has to be taken offline for maint work, or unexpectedly fail. We need a quick way to disable the integration tests if we decide we don't want to have pipelines queued until the runner comes back online. Both these problems can be addressed by requiring a environment variable to be set LIBVIRT_CI_INTEGRATION=1 This can be done in the GitLab repo CI settings for permanent enablement. Alternatively it can be set for individual scheduled jobs, or using a push option git push -o ci.variable=LIBVIRT_CI_INTEGRATION=1 Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
Libvirt API for virtualization
Libvirt provides a portable, long term stable C API for managing the virtualization technologies provided by many operating systems. It includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER Hypervisor.
For some of these hypervisors, it provides a stateful management daemon which runs on the virtualization host allowing access to the API both by non-privileged local users and remote users.
Layered packages provide bindings of the libvirt C API into other languages including Python, Perl, PHP, Go, Java, OCaml, as well as mappings into object systems such as GObject, CIM and SNMP.
Further information about the libvirt project can be found on the website:
License
The libvirt C API is distributed under the terms of GNU Lesser
General Public License, version 2.1 (or later). Some parts of the code
that are not part of the C library may have the more restrictive GNU
General Public License, version 2.0 (or later). See the files
COPYING.LESSER and COPYING for full license
terms & conditions.
Installation
Instructions on building and installing libvirt can be found on the website:
https://libvirt.org/compiling.html
Contributing
The libvirt project welcomes contributions in many ways. For most components the best way to contribute is to send patches to the primary development mailing list. Further guidance on this can be found on the website:
https://libvirt.org/contribute.html
Contact
The libvirt project has two primary mailing lists:
- libvirt-users@redhat.com (for user discussions)
- libvir-list@redhat.com (for development only)
Further details on contacting the project are available on the website: