From da3767cb629b5a9f54629990eb31c3a01439e821 Mon Sep 17 00:00:00 2001 From: Alex Iribarren <Alex.Iribarren@cern.ch> Date: Tue, 16 Feb 2021 11:21:45 +0100 Subject: [PATCH] Fix links --- docs/koji/bootstrapping.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/koji/bootstrapping.md b/docs/koji/bootstrapping.md index 2f91ae4..3cd7546 100644 --- a/docs/koji/bootstrapping.md +++ b/docs/koji/bootstrapping.md @@ -296,7 +296,7 @@ You will start to run into dependency loops now (rpmci assumes you have a Docker the new distro, but you haven't created CERN Docker images for this distro yet because you still don't have the base RPMs, etc.) You'll have to figure out how to bootstrap your way out of it depending on the case. You can use an upstream Docker image to start with and -then eventually replace it, you can build with a different Docker image temporarily, +then eventually replace it, you can build with a different but similar Docker image temporarily, you can build the bare minimum RPMs you need by hand... I'm sure you can figure something out. You may need to temporarily disable the tests of some of the RPMs you'll build later on, @@ -346,12 +346,13 @@ you can build cloud and Docker images. [`cern-wrappers`](https://gitlab.cern.ch/linuxsupport/rpms/cern-wrappers) is installed in the Docker and cloud images, so it needs to be built now. -Additionally, `cern-linuxsupport-access`, `phonebook` and `useraddcern` are installed +Additionally, [`cern-linuxsupport-access`](https://gitlab.cern.ch/linuxsupport/rpms/cern-linuxsupport-access), +[`phonebook`](https://gitlab.cern.ch/linuxsupport/rpms/phonebook) and [`useraddcern`](https://gitlab.cern.ch/linuxsupport/rpms/useraddcern) are installed as part of the [CERN functional tests](https://gitlab.cern.ch/linuxsupport/testing/cern_centos_functional_tests/-/blob/master/tests/cern_basic/1_yum_installs.sh) (which will run against the Docker image to validate it), so they have to be built now. -`epel-release` may be needed by the rpmci Docker images, if it exists and makes sense -for your new distro. +[`epel-release`](https://gitlab.cern.ch/linuxsupport/rpms/releases/epel-release) may +be needed by the rpmci Docker images, if it exists and makes sense for your new distro. ## Create tag for openafs @@ -454,13 +455,13 @@ adapt it as needed. Make sure you have some tests to make sure your built Docker image works as you expect. Once you have a working Docker image, you can create a scheduled pipeline to -(rebuild it every month)[https://gitlab.cern.ch/linuxsupport/c8-base/-/pipeline_schedules]. +[rebuild it every month](https://gitlab.cern.ch/linuxsupport/c8-base/-/pipeline_schedules). ## Build a new worker image for rpmci Now that you have a real Docker image for your new distro, you should get rpmci to use it. You'll have to build an rpmci worker image based off of it and -(integrate it)[https://gitlab.cern.ch/linuxsupport/rpmci/-/compare/8e9d5203...db470a66] into rpmci. +[integrate it](https://gitlab.cern.ch/linuxsupport/rpmci/-/compare/8e9d5203...db470a66) into rpmci. Once that is done, you can go back through all the previous RPMs you created where you had to disable the tests and enable them again. Now that your image is -- GitLab