[
https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri updated OVIRT-1385:
-----------------------------
Resolution: Won't Do
Status: Done (was: To Do)
[~vojtech] as [[email protected]] mock_runner is in stabilization mode and
we're not planning any new features there, if this is something that is still
needed, we can check if its possible to support via V2 of future work planned
for the CI
> 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: oVirt CI
> 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
(v1001.0.0-SNAPSHOT#100086)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/SCFKR74EGLONXV6DZNNPHAUDOWDFWSM4/
