Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-18 Thread Christophe Fergeau
On Wed, Oct 18, 2017 at 09:51:56AM +0300, Yedidyah Bar David wrote: > > Filed for this, so that we do not forget it: > > https://bugzilla.redhat.com/show_bug.cgi?id=1503441 Thanks! > > It's still not a replacement for oVirt's needs - so please > consider/review/ack also current patch. Thanks.

Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-17 Thread Yedidyah Bar David
On Tue, Oct 17, 2017 at 12:30 PM, Christophe Fergeau wrote: > On Mon, Oct 16, 2017 at 05:01:14PM +0300, Yedidyah Bar David wrote: >> On Mon, Oct 16, 2017 at 4:16 PM, Yedidyah Bar David wrote: >> > On Mon, Oct 16, 2017 at 4:07 PM, Christophe Fergeau >> > wrote: >> >> My understanding is that the

Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-17 Thread Christophe Fergeau
On Mon, Oct 16, 2017 at 05:01:14PM +0300, Yedidyah Bar David wrote: > On Mon, Oct 16, 2017 at 4:16 PM, Yedidyah Bar David wrote: > > On Mon, Oct 16, 2017 at 4:07 PM, Christophe Fergeau > > wrote: > >> My understanding is that the short log really should be saying "oVirt CI > >> support" rather t

Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-16 Thread Yedidyah Bar David
On Mon, Oct 16, 2017 at 4:16 PM, Yedidyah Bar David wrote: > On Mon, Oct 16, 2017 at 4:07 PM, Christophe Fergeau > wrote: >> My understanding is that the short log really should be saying "oVirt CI >> support" rather than "standard CI support". > > Changed to 'standard oVirt CI support' and adde

Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-16 Thread Yedidyah Bar David
On Mon, Oct 16, 2017 at 4:07 PM, Christophe Fergeau wrote: > My understanding is that the short log really should be saying "oVirt CI > support" rather than "standard CI support". Changed to 'standard oVirt CI support' and added a link. oVirt has also non-standard CI, which is currently used for

Re: [Spice-devel] [NSIS] automation: add standard ci support

2017-10-16 Thread Christophe Fergeau
My understanding is that the short log really should be saying "oVirt CI support" rather than "standard CI support". Has gitlab built-in CI been considered for this work? In other words, why use oVirt for CI rather than something more "standard"? Where would the error messages go if CI fails? Are

[Spice-devel] [NSIS] automation: add standard ci support

2017-10-16 Thread Yedidyah Bar David
From: Sandro Bonazzola This patch was previously merged in ovirt gerrit with Change-Id Ie16cc0902c4393e62b074661a86f2f5bb9a1efc1, but removed from master branch there for review on spice-devel. Change-Id: I042f30d87b0730ae76e2c8b537e46a56cbbf65f7 Signed-off-by: Sandro Bonazzola --- automation/

[Spice-devel] [NSIS] automation: add standard ci support

2017-10-16 Thread Yedidyah Bar David
From: Sandro Bonazzola Change-Id: Ie16cc0902c4393e62b074661a86f2f5bb9a1efc1 Signed-off-by: Sandro Bonazzola --- automation/build-artifacts.packages | 15 +++ automation/build-artifacts.repos| 3 +++ automation/build-artifacts.sh | 23 +++ automation/ch