[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.p... ] Vojtech Szocs updated OVIRT-1385: --------------------------------- Description: 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. was: There are multiple oVirt projects [1] 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} [1] 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 configurable per-project. Not sure what's the best approach here, please advise.
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: By-EMAIL Reporter: Vojtech Szocs Assignee: infra
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)
participants (1)
-
Vojtech Szocs (oVirt JIRA)