July 2016 - Infra - oVirt List Archives

premissions for my jenkins user
by Ido Rosenzwig 19 Jul '16

19 Jul '16

Hi, I wish to have trigger (and re-trigger) premissions on my jenkins user. my user is : irosenzw Best regards, Ido Rosenzwig

3 2

[oVirt Jenkins] ovirt-engine_master_upgrade-from-4.0_el7_merged - Build # 607 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jul '16

19 Jul '16

------=_Part_372_1464967305.1468923704578 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build Number: 607 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/60929 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #607 [Yevgeny Zaspitsky] engine: remove unsused code from VmNicValidator ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_372_1464967305.1468923704578--

1 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-4.0_el7_merged - Build # 604 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jul '16

19 Jul '16

------=_Part_366_914306850.1468920336976 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… Build Number: 604 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/60923 ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_366_914306850.1468920336976--

1 0

[oVirt Jenkins] ovirt-engine_4.0_upgrade-from-3.6_el7_merged - Build # 315 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jul '16

19 Jul '16

------=_Part_364_974188423.1468918828994 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_4.0_upgrade-from-3.6_el7_merged/3… Build Number: 315 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/58286 ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_364_974188423.1468918828994--

1 0

ovirt-engine_master_coverity-analysis is broken
by Barak Korren 19 Jul '16

19 Jul '16

Hi Sharon, The $subject job started failing and Eyal told me you worked on it recently. I'm not sure your changed made it fail because I saw changes by both you and Sandro. Anyway the problem with the jobs seems to be that the jenkins repo URL was set to: git:///jenkins.git Instead of: git://gerrit.ovirt.org/jenkins.git I fixed this manually but it is still failing. Now it seems that it is not getting the right thing from: https://scan.coverity.com/download/linux-64 I can't find any docs about this when looking quickly at coverity`s website, so I'm hoping you know more about this. -- Barak Korren bkorren(a)redhat.com RHEV-CI Team

4 6

[JIRA] (OVIRT-641) Build oVirt 4.0.2 RC1
by sbonazzo (oVirt JIRA) 19 Jul '16

19 Jul '16

sbonazzo created OVIRT-641: ------------------------------ Summary: Build oVirt 4.0.2 RC1 Key: OVIRT-641 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-641 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.148.3#100005)

1 0

oVirt 4.0.2 RC1 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 19 Jul '16

19 Jul '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.2, tr: 4.0.2) A list of bugs that require attention is here: - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

RHEVM CI Jenkins daily report - 18
by jenkins＠jenkins.phx.ovirt.org 18 Jul '16

18 Jul '16

------=_Part_362_1346657207.1468882803657 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/18//artifact/exported-ar… Cheers, Jenkins ------=_Part_362_1346657207.1468882803657 Content-Type: application/octet-stream; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 18/07/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc23-x86_64/">ovirt-engine_3.6_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_coverity-analysis/">ovirt-engine_master_coverity-analysis</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc24-x86_…">ovirt-node-ng_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-fc23-x…">ovirt-node-ng_ovirt-3.6_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-x…">ovirt-node-ng_ovirt-4.0_build-artifacts-fc22-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-fc23-x…">ovirt-node-ng_ovirt-4.0_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_ovirt-3.6_chec…">ovirt-node-plugin-hosted-engine_ovirt-3.6_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc24-x86_64/">vdsm_master_check-merged-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_362_1346657207.1468882803657--

1 0

[Jenkins] Passing parameters to build-artifacts.sh
by Vojtech Szocs 18 Jul '16

18 Jul '16

Hi, I'm just curious whether it's possible to do the following: Let's say we have a project (ovirt-engine-dashboard) built by Jenkins, which means there's a Jenkins job that runs build-artifacts.sh script whenever a patch gets merged via gerrit. Can we somehow pass custom parameters to build-artifacts.sh for such (Jenkins CI) builds? For example, putting something like this into commit message: My-Param 123 would reflect into `My-Param` env. variable when running the script? Motivation: for release builds (which shouldn't contain the "snapshot" part [*] in RPM release string), pass parameter to build-artifacts.sh that ensures the "snapshot" part is empty. This way, we don't need to patch the project prior to release (remove "snapshot" in spec) & then patch it again after the release (re-add "snapshot" in spec). [*] {date}git{commit} Thanks, Vojtech

6 8

Re: Forgotten Patches in project ovirt-engine
by Michal Skrivanek 18 Jul '16

18 Jul '16

can you please abandon this and any other Eldan’s patches which are still out there? They have been already addressed by other means Thanks, michal > On 17 Jul 2016, at 03:56, noreply+patchwatcher(a)ovirt.org wrote: > > The following patches did not have any activity for over 90 days, please consider nudging for more attention. > http://gerrit.ovirt.org/42867 > >

3 3