Re: [libvirt] [jenkins-ci PATCH v2 1/2] projects: Add default machines for libvirt-dbus
On Tue, Aug 21, 2018 at 12:38:05PM +0200, Andrea Bolognani wrote:
This doesn't change the results but brings it more in line
with how other projects are defined and will help us out
later.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
projects/libvirt-dbus.yaml | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/projects/libvirt-dbus.yaml b/projects/libvirt-dbus.yaml
index f01ea9e..fdfb615 100644
--- a/projects/libvirt-dbus.yaml
+++ b/projects/libvirt-dbus.yaml
@@ -1,20 +1,20 @@
- project:
name: libvirt-dbus
+ machines:
+ - libvirt-centos-7
+ - libvirt-debian-9
+ - libvirt-fedora-27
+ - libvirt-fedora-28
+ - libvirt-fedora-rawhide
+ - libvirt-freebsd-10
+ - libvirt-freebsd-11
title: Libvirt D-Bus
archive_format: xz
git-url: https://github.com/libvirt/libvirt-dbus.git
jobs:
- autotools-build-job:
parent_jobs: 'libvirt-glib-master-build'
- machines:
- - libvirt-centos-7
- - libvirt-debian-9
- - libvirt-fedora-27
- - libvirt-fedora-28
- - libvirt-fedora-rawhide
- - libvirt-freebsd-10
- - libvirt-freebsd-11
- autotools-syntax-check-job:
parent_jobs: 'libvirt-dbus-master-build'
machines:
I wish there was something like exclusion, so that when we want to exclude just
a single machine from the default machine list defined for the project (or
from {all_machines} for that matter), we don't have to override the whole
machine list all over again minus the ones we can't/don't want to use.
Anyway,
Reviewed-by: Erik Skultety <eskultet(a)redhat.com>