oVirt infra daily report - unstable production jobs - 324
by jenkins@jenkins.phx.ovirt.org
------=_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...
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;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_4_1910983634.1494975603620--
7 years, 6 months
[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ]
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)
7 years, 6 months
[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ]
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)
7 years, 6 months
[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ]
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)
7 years, 6 months