Jenkins build is back to normal : ovirt_master_publish-rpms_nightly #317

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #316

See -- Started by user Fabian Deutsch Building on master in workspace [WS-CLEANUP] Deleting project workspace... [WS-C

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1846 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1846/ Build Number: 1846 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/52814 --

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 1847 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1847/ Build Number: 1847 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48251

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1970 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1970/ Build Number: 1970 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/4816

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 1969 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1969/ Build Number: 1969 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/52815 ---

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #315

See -- Started by user Fabian Deutsch Building on master in workspace [WS-CLEANUP] Deleting project workspace... [ovir

Re: 3.6.3 bugs are wrongly moved to MODIFIED

David, Is it something manual we need to change per version or we can add something automatic to work on any 3.6.X branch only (exluding the 3.6 branch)? e. On Thu, Jan 28, 2016 at 4:00 PM, Tal Nisan wrote: > This was the behavior in 3.6.2, don't know why it changed > > On Thu, Jan 28, 2016 at

Re: 3.6.3 bugs are wrongly moved to MODIFIED

This was the behavior in 3.6.2, don't know why it changed On Thu, Jan 28, 2016 at 3:57 PM, Eyal Edri wrote: > so maybe we'll stop moving bugs to MODIFIED if they are merged on stable > branch (i.e ovirt-engine-3.6) and only if its merged into a version branch > (i.e ovirt-engine-3.6.3) ? > > On

Re: 3.6.3 bugs are wrongly moved to MODIFIED

so maybe we'll stop moving bugs to MODIFIED if they are merged on stable branch (i.e ovirt-engine-3.6) and only if its merged into a version branch (i.e ovirt-engine-3.6.3) ? On Thu, Jan 28, 2016 at 3:52 PM, Tal Nisan wrote: > It makes life easier for everyone when automation moves the bug to >

Re: 3.6.3 bugs are wrongly moved to MODIFIED

It makes life easier for everyone when automation moves the bug to MODIFIED, if the work is not done then the developer can always move it back to POST like we sometimes do. In any way, when a 3.6.3 bug is merged in 3.6.3 it should be moved to MODIFIED, not a second before On Thu, Jan 28, 2016 at

Re: 3.6.3 bugs are wrongly moved to MODIFIED

On Thu, Jan 28, 2016 at 10:59 AM, Eyal Edri wrote: > > > On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David > wrote: >> >> On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote: >> > Maybe we should change the logic on moving bugs to MODIFIED, >> > Now that we moved to the version branch. >> > >>

Re: Adding access rights to yaml file

Maybe i'm missing something, but isn't the role plugin in jenkins does exactly that? [1] [1]http://docs.openstack.org/infra/jenkins-job-builder/properties.html On Wed, Jan 27, 2016 at 12:17 PM, Sandro Bonazzola wrote: > Hi, > can you please add support for access rights to jenkins jobs to yam

Logwatch for linode01.ovirt.org (Linux)

### Logwatch 7.3.6 (05/19/07) Processing Initiated: Thu Jan 28 04:27:16 2016 Date Range Processed: yesterday ( 2016-Jan-27 ) Period is day. Detail Level of Output: 0

Re: 3.6.3 bugs are wrongly moved to MODIFIED

On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David wrote: > On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote: > > Maybe we should change the logic on moving bugs to MODIFIED, > > Now that we moved to the version branch. > > > > Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED t

Re: [oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 827 - Still Failing!

IIRC we merged the rpmdb fix, I took the slave offline for now, we'll need to check if this job uses the new cleanup code for rpmdb. e. On Thu, Jan 28, 2016 at 10:39 AM, Yedidyah Bar David wrote: > On Thu, Jan 28, 2016 at 10:34 AM, wrote: > > Project: > http://jenkins.ovirt.org/job/ovirt-eng

Re: [oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 827 - Still Failing!

On Thu, Jan 28, 2016 at 10:34 AM, wrote: > Project: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ > Build: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/827/ > Build Number: 827 > Build Status: Still Failing > Triggered By: Triggered

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 827 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/827/ Build Number: 827 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/52807

Re: 3.6.3 bugs are wrongly moved to MODIFIED

On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote: > Maybe we should change the logic on moving bugs to MODIFIED, > Now that we moved to the version branch. > > Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED that we'll > be sure its OK? Repeating myself from a previous discussion

Re: 3.6.3 bugs are wrongly moved to MODIFIED

Maybe we should change the logic on moving bugs to MODIFIED, Now that we moved to the version branch. Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED that we'll be sure its OK? e. On Thu, Jan 28, 2016 at 10:03 AM, Tal Nisan wrote: > After merging a patch for a 3.6.3 bug on the

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 826 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/826/ Build Number: 826 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/52800 --

3.6.3 bugs are wrongly moved to MODIFIED

After merging a patch for a 3.6.3 bug on the ovirt-engine-3.6 branch the bug is moved to MODIFIED, since the 3.6.3 branch was opened yesterday the bug should stay in POST until merged in ovirt-engine-3.6.3 branch as well ___ Infra mailing list Infra@ovirt