Won't Do
Details
Assignee
infrainfraReporter
Vojtech SzocsVojtech Szocs(Deactivated)Components
Priority
Low
Details
Details
Assignee
infra
infraReporter
Vojtech Szocs
Vojtech Szocs(Deactivated)Components
Priority
Created May 16, 2017 at 4:46 PM
Updated June 4, 2018 at 6:29 AM
Resolved June 3, 2018 at 1:00 PM
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:# 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}
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 https://ovirt-jira.atlassian.net/browse/OVIRT-921#icft=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.