Re: Change in ovirt-engine[ovirt-engine-3.6]: packaging: engine-backup: recreate dwh conf only if found

2016-03-09 Thread Yedidyah Bar David
On Wed, Mar 9, 2016 at 6:42 PM, Jenkins CI wrote: > Jenkins CI has posted comments on this change. > > Change subject: packaging: engine-backup: recreate dwh conf only if found > .. > > > Patch Set 1: >

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #378

2016-03-09 Thread jenkins
See -- Started by timer Building on master in workspace [WS-CLEANUP] Deleting project workspace...

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

2016-03-09 Thread jenkins
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/2228/ Build Number: 2228 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/50567

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

2016-03-09 Thread jenkins
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/2227/ Build Number: 2227 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/50568

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

2016-03-09 Thread jenkins
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/2342/ Build Number: 2342 Build Status: Still Failing Triggered By: Triggered by Gerrit:

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

2016-03-09 Thread jenkins
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/2341/ Build Number: 2341 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/50568

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

2016-03-09 Thread jenkins
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// Build Number: Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/50565

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

2016-03-09 Thread jenkins
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/2336/ Build Number: 2336 Build Status: Still Failing Triggered By: Triggered by Gerrit:

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

2016-03-09 Thread jenkins
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/2221/ Build Number: 2221 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/50566

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

2016-03-09 Thread jenkins
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/2335/ Build Number: 2335 Build Status: Still Failing Triggered By: Triggered by Gerrit:

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

2016-03-09 Thread jenkins
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/2334/ Build Number: 2334 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53152

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

2016-03-09 Thread jenkins
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/2220/ Build Number: 2220 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53152

Re: [oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - Build # 953 - Failure!

2016-03-09 Thread Gil Shinar
Hi, There's the follwoing error message: *+ engine-setup --config-append=/home/jenkins/workspace/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/jenkins/jobs/ovirt-engine_upgrade_to_3.6/setup.file.otopi [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files:

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

2016-03-09 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/953/ Build Number: 953 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/54552

Re: yamlizing findbugs jobs

2016-03-09 Thread David Caro Estevez
On 03/09 15:32, Eyal Edri wrote: > On Wed, Mar 9, 2016 at 3:31 PM, David Caro Estevez wrote: > > > On 03/09 15:28, Eyal Edri wrote: > > > Isn't there a plugin like x-unit for findbugs that can just get XML file > > > and present the graphs? > > > for the alerts on limit maybe

Re: yamlizing findbugs jobs

2016-03-09 Thread Eyal Edri
On Wed, Mar 9, 2016 at 3:31 PM, David Caro Estevez wrote: > On 03/09 15:28, Eyal Edri wrote: > > Isn't there a plugin like x-unit for findbugs that can just get XML file > > and present the graphs? > > for the alerts on limit maybe we can implement something ourselves. > >

Re: yamlizing findbugs jobs

2016-03-09 Thread David Caro Estevez
On 03/09 15:28, Eyal Edri wrote: > Isn't there a plugin like x-unit for findbugs that can just get XML file > and present the graphs? > for the alerts on limit maybe we can implement something ourselves. There is, the issue is that if that xml file does not exist it fails the job, so it's not

Re: yamlizing findbugs jobs

2016-03-09 Thread Eyal Edri
Isn't there a plugin like x-unit for findbugs that can just get XML file and present the graphs? for the alerts on limit maybe we can implement something ourselves. On Wed, Mar 9, 2016 at 3:21 PM, David Caro Estevez wrote: > On 03/09 15:19, Eyal Edri wrote: > > I think the

Re: yamlizing findbugs jobs

2016-03-09 Thread Eyal Edri
I think the idea is to add report.html generic file that will show anything we'd like. Having said that, it might be too complex or overkill to do it right now just for findbugs, so maybe we can still use the findbugs plugin and provide the xml file (?) to the plugin? Maybe we can use [1] as a

Re: yamlizing findbugs jobs

2016-03-09 Thread David Caro Estevez
On 03/09 15:19, Eyal Edri wrote: > I think the idea is to add report.html generic file that will show anything > we'd like. > Having said that, it might be too complex or overkill to do it right now > just for findbugs, so maybe we can still use the findbugs plugin and > provide the xml file (?) >

Re: yamlizing findbugs jobs

2016-03-09 Thread David Caro Estevez
On 03/09 15:57, Sandro Bonazzola wrote: > About https://gerrit.ovirt.org/#/c/46925/ > > > *Juan Hernandez* Mar 7 5:34 PM > > Patch Set 14: > > The only important thing that is missing is what will happen with the > findbugs reports. Will we still have a report that tells us what bugs > exist,