[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
Barak Korren (oVirt JIRA)
jira at ovirt-jira.atlassian.net
Wed Jan 10 08:00:48 UTC 2018
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barak Korren updated OVIRT-1835:
--------------------------------
Component/s: (was: oVirt CI)
Jenkins Slaves
> Create an automated update mechanism for slaves
> -----------------------------------------------
>
> Key: OVIRT-1835
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Slaves
> Reporter: Barak Korren
> Assignee: infra
> Labels: slaves
>
> While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.
> Some things we'd like such a mechanism to provide:
> * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed).
> * Test updated slaves before putting them back to production use
> * Allow rolling back failed updates
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20180110/8bca266d/attachment.html>
More information about the Infra
mailing list