May 2017 - Infra - oVirt List Archives

Fwd: UPDATE: Bugzilla 5 beta server is back online
by Sandro Bonazzola 18 May '17

18 May '17

---------- Forwarded message ---------- From: Christine Freitas <cfreitas(a)redhat.com> Date: Mon, May 15, 2017 at 6:03 PM Subject: UPDATE: Bugzilla 5 beta server is back online Hello All, The Bugzilla 5 beta server [1] is back online. We encourage you to test your current scripts and take part in the beta discussions on the Fedora development list [2]. Partners and customers may also use their existing communications channels to share feedback or questions. We've extended the beta window and ask that you provide feedback or questions by Wednesday, June 14th. The official release date for Bugzilla 5 will be determined based on the beta feedback. We will communicate to you as the beta continues to progress. For more information refer to: https://beta-bugzilla.redhat.com/page.cgi?id=whats-new.html https://beta-bugzilla.redhat.com/page.cgi?id=release-notes.html https://beta-bugzilla.redhat.com/page.cgi?id=faq.html https://beta-bugzilla.redhat.com/docs/en/html/using/index.html https://beta-bugzilla.redhat.com/docs/en/html/api/index.html Cheers, the Red Hat Bugzilla team. 1: https://beta-bugzilla.redhat.com/ 2: https://lists.fedoraproject.org/archives/list/devel%40lists. fedoraproject.org/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

oVirt infra daily report - unstable production jobs - 325
by jenkins＠jenkins.phx.ovirt.org 18 May '17

18 May '17

------=_Part_28_917056408.1495062007393 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/325//artifact/exported-a… Cheers, Jenkins ------=_Part_28_917056408.1495062007393 Content-Type: text/html; charset=us-ascii; 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 - 17/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</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_master_hc-system-tests/">ovirt_master_hc-system-tests</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_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</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_28_917056408.1495062007393--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6728 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 17 May '17

17 May '17

------=_Part_24_100261321.1495046797951 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6728/, Build Number: 6728, Build Status: FAILURE ------=_Part_24_100261321.1495046797951--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6726 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 17 May '17

17 May '17

------=_Part_19_989713850.1495042654678 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6726/, Build Number: 6726, Build Status: FAILURE ------=_Part_19_989713850.1495042654678--

1 1

[JIRA] (OVIRT-1386) grant me with permissions in both staging Jenkins and Gerrit
by Gil Shinar (oVirt JIRA) 17 May '17

17 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1386?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1386: --------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > grant me with permissions in both staging Jenkins and Gerrit > ------------------------------------------------------------ > > Key: OVIRT-1386 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1386 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Please grant me with permissions to the staging Jenkins gshinar(a)redhat.com > and to the staging Gerrit -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1386) grant me with permissions in both staging Jenkins and Gerrit
by Gil Shinar (oVirt JIRA) 17 May '17

17 May '17

Gil Shinar created OVIRT-1386: --------------------------------- Summary: grant me with permissions in both staging Jenkins and Gerrit Key: OVIRT-1386 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1386 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra Please grant me with permissions to the staging Jenkins gshinar(a)redhat.com and to the staging Gerrit -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

oVirt infra daily report - unstable production jobs - 324
by jenkins＠jenkins.phx.ovirt.org 17 May '17

17 May '17

------=_Part_4_1910983634.1494975603620 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/324//artifact/exported-a… Cheers, Jenkins ------=_Part_4_1910983634.1494975603620 Content-Type: text/html; charset=us-ascii; 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 - 16/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</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_4_1910983634.1494975603620--

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Labels: mock_runner.sh (was: ) > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > Labels: mock_runner.sh > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Component/s: Jenkins > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA) 16 May '17

16 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1385: -------------------------------- Priority: Low (was: Medium) > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0