[libvirt] [PATCH jenkins-ci 17/19] projects: add the virt-manager package

Andrea Bolognani abologna at redhat.com
Fri Aug 5 08:11:12 UTC 2016


On Thu, 2016-08-04 at 15:52 +0100, Daniel P. Berrange wrote:
> Add a project defining the virt-manager package build jobs
> 
> Signed-off-by: Daniel P. Berrange <berrange at redhat.com>
> ---
>  projects/virt-manager.yaml | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
>  create mode 100644 projects/virt-manager.yaml
> 
> diff --git a/projects/virt-manager.yaml b/projects/virt-manager.yaml
> new file mode 100644
> index 0000000..101a76c
> --- /dev/null
> +++ b/projects/virt-manager.yaml
> @@ -0,0 +1,19 @@
> +
> +- project:
> +    name: virt-manager
> +    machines:
> +      - libvirt-centos-7
> +      - libvirt-fedora-21
> +      - libvirt-fedora-22
> +      - libvirt-fedora-23
> +      - libvirt-fedora-rawhide

I'm using virt-manager as an example here, but the question
actually applies to most of the jobs: why are we not building
this on more machines? The current job[1] is running on
libvirt-centos-6 in addition to the ones you listed, so that
should be included as well.

However, I see no reason why we shouldn't be running this on
libvirt-debian and libvirt-freebsd as well. I guess we want
to be as close as possible to the manually-created setup at
first, and build on that over time...

> +    title: Libvirt Python
> +    jobs:
> +      - python-distutils-build-job:
> +          parent_jobs:
> +            - 'libvirt-python-build'
> +            - 'libosinfo-build'
> +      - python-distutils-check-job:
> +          parent_jobs: 'virt-manager-build'
> +      - python-distutils-rpm-job:
> +          parent_jobs: 'virt-manager-check'

[1] https://ci.centos.org/view/libvirt-project/job/virt-manager-build/
-- 
Andrea Bolognani / Red Hat / Virtualization




More information about the libvir-list mailing list