[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-1835: ---------------------------------- I'm not sure we need to invest in this if the aim is to more to ephemeral slaves, either containers or VMs. > 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#100095) _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)ovirt.org 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/infra@ovirt.org/message/HQPCHBNAIGF...