Build failed in Jenkins: publish_ovirt_rpms_nightly_master #40

See -- Started by user Sandro Bonazzola Building on master in workspace [publish_ovirt_rpms_nightly_master] $ /bin/sh -

Build failed in Jenkins: publish_ovirt_rpms_nightly_master #39

See -- Started by user Sandro Bonazzola Building on master in workspace [publish_ovirt_rpms_nightly_master] $ /bin/sh -

Weird timing on jenkins slave

Hi, I'm looking at: http://jenkins.ovirt.org/job/ovirt-engine_master_create_rpms/label=fedora19-host/1619/console 05:08:14 [INFO] Compiling permutation 0... 05:08:14 [INFO] Compiling permutation 1... 05:08:14 [INFO] Compiling permutation 2... 05:08:14 [INFO] Compiling perm

Build failed in Jenkins: publish_ovirt_rpms_nightly_master #38

See -- Started by timer Building on master in workspace [publish_ovirt_rpms_nightly_master] $ /bin/sh -xe /tmp/hudson7

Build failed in Jenkins: publish_ovirt_rpms_nightly #695

See -- Started by timer Building remotely on jenkins-slave-host04.ovirt.org in workspace [publish_ovirt_rpms_nightly] $ /bin/sh -xe

Fwd: Your message to Automation awaits moderator approval

This is an automated reply I got after commenting on a patch where the gerrit-hooks script acted. Can we disable email notifications to this account? They seem pretty useless. Thanks, Allon - Forwarded Message - > From: automation-boun...@ovirt.org > To: amure...@redhat.com > Sent: Wed

Re: [node-devel] oVirt Node + VDSM Jenkins builder

Am Mittwoch, den 26.02.2014, 12:01 -0500 schrieb Ryan Barry: > Adding a single plugin to the image should be much less troublesome > than > the jobs we had which built an ISO on every commit, but I'd like to > avoid overloading Jenkins as much as possible while still fulfilling > the > intended

Re: pyflakes and pep8 from pip?

On Wed, Feb 26, 2014 at 03:14:30PM +0100, Fabian Deutsch wrote: > we are using pyflakes and pep8 to check oVirt Node patches. > One problem we have is that there are different pyflakes/pep8 version > son the different slaves. > E.g. this job fails because older pyflakes versions handle _() > difere

pyflakes and pep8 from pip?

Hey, we are using pyflakes and pep8 to check oVirt Node patches. One problem we have is that there are different pyflakes/pep8 version son the different slaves. E.g. this job fails because older pyflakes versions handle _() diferently: http://jenkins.ovirt.org/job/ovirt-node-devel-check/1893/conso

Re: oVirt Node filesystem layout on resources.ovirt.org

Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko: > We are moving to a new layout resources.ovirt.org/pub. > > Please let us know where do you want to put your files. For that case I'd suggest: pub + ovirt-node-base-3.0 + iso + rpm + src + ovirt-node-base-stable (symlink to ov

Re: oVirt Node filesystem layout on resources.ovirt.org

We are moving to a new layout resources.ovirt.org/pub. Please let us know where do you want to put your files. - Kiril - Original Message - > From: "Fabian Deutsch" > To: infra@ovirt.org > Cc: "node-devel" > Sent: Wednesday, February 26, 2014 10:18:27 AM > Subject: oVirt Node filesyste

oVirt Node filesystem layout on resources.ovirt.org

Hey, currently it is not easy to find oVirt Node (Base Image) releases on resources.o.o - I'd like to suggest a layout simplification to remove some clutter, improve the findability of isos and ease the maintenance. Currently the (Node related) layout is: releases + base + node-base + 3.0.0