Jenkins build is back to normal : system-sync_mirrors-centos-base-el6-x86_64 #1137

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

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 59 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64/59/ Build Number: 59 Build Status: Fixed Triggered By: Started by user Sandro Bonazzola, Started by user

Jenkins build is back to normal : system-sync_mirrors-fedora-updates-fc24-x86_64 #1053

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

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc24-x86_64 #1052

See Changes: [Barak Korren] Made clone url for 'jenkins' customizable -- Started by timer [EnvInject] - Loading node environment variables.

Build failed in Jenkins: system-sync_mirrors-centos-base-el6-x86_64 #1136

See Changes: [Barak Korren] Made clone url for 'jenkins' customizable -- Started by timer [EnvInject] - Loading node environment variables.

[CQ]: 86679,4 (otopi) failed "ovirt-master" system tests

Change 86679,4 (otopi) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the

[CQ]: 86865, 8 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 86865,8 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change

Re: [CQ]: 86865, 8 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause

On Mon, Jan 29, 2018 at 1:47 PM, oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 86865,8 (otopi) failed. However, this change seems not to be the root cause > for > this failure. Change 86679,4 (otopi) that this change depends

PHX planned maintenance 29.01.2018 @19:00 GMT

Hi everyone, Planned works are going to be performed in the PHX data center today. They are related to core networking hardware upgrades and may cause short connectivity loss to services hosted by the oVirt project, including: * Jenkins CI * Package repositories * project website * mailing lists

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 20 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/20/ Build Number: 20 Build Status: Failure Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 168 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/168/ Build Number: 168 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 174 - Still Failing!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/174/ Build Number: 174 Build Status: Still Failing Triggered By: Started by timer - Changes Since

[CQ]: 86869, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 86869,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 86679,4 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 58 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64/58/ Build Number: 58 Build Status: Failure Triggered By: Started by timer

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1866: Component/s: Jenkins Master > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY >

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

Daniel Belenky created OVIRT-1866: - Summary: Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY Key: OVIRT-1866 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 Project: oVirt -

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Belenky updated OVIRT-1866: -- Epic Link: OVIRT-400 > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY >

Re: PHX planned maintenance 29.01.2018 @19:00 GMT

Maintenance is complete with minimal downtime. CI is resumed and all services should be reachable. If any jobs failed to get queued for you - feel free to re-trigger. For other issues please log a Jira ticket. Regards, Evgheni On Mon, Jan 29, 2018 at 2:13 PM, Evgheni Dereveanchin