From 26bc345fbfbbd2ee1e775b5fc9c2b324d408d648 Mon Sep 17 00:00:00 2001 From: Mohan Boddu Date: Oct 08 2019 15:36:59 +0000 Subject: SOP for koji archiving Signed-off-by: Mohan Boddu --- diff --git a/docs/sysadmin-guide/sops/koji-archive.rst b/docs/sysadmin-guide/sops/koji-archive.rst new file mode 100644 index 0000000..b47cf15 --- /dev/null +++ b/docs/sysadmin-guide/sops/koji-archive.rst @@ -0,0 +1,30 @@ +This SOP documents how to archive Fedora EOL'd builds from the DEFAULT volume to archived volume. + +Before archiving the builds, identify if any of the EOL'd release builds are still being used in the current releases. +For example. to test if f28 builds are still being using in f32, use: + +$ koji list-tagged f32 | grep fc28 + +Tag all these builds to koji's do-not-archive-yet tag, so that they wont be archived. To do that, first add the packages to the do-not-archive-tag + +$ koji add-pkg do-not-archive-yet --owner pkg1 pkg2 ... + +Then tags the builds to do-not-archive-yet tag + +$ koji tag-build do-not-archive-yet build1 build2 ... + +Then update the archive policy which is available in releng repo (https://pagure.io/releng/blob/master/f/koji-archive-policy) + +Run the following from compose-x86-01.phx2.fedoraproject.org + +$ cd +$ wget https://pagure.io/releng/raw/master/f/koji-archive-policy +$ git clone https://pagure.io/koji-tools/ +$ cd koji-tools +$ ./koji-change-volumes -p compose_koji -v ~/archive-policy + +In any case, if you need to move a build back to DEFAULT volume + +$ koji add-pkg do-not-archive-yet --owner pkg1 +$ koji tag-build do-not-archive-yet build1 +$ koji set-build-volume DEFAULT