From 4c29401c731d6d37f9aed102d83fe7fd9f01769a Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Sep 15 2025 14:35:06 +0000 Subject: coreos/cincinnati: Update guide based on recent changes We now build via the `main` branch [1] so let's update the docs here to remove some necessary steps. [1] https://pagure.io/fedora-infra/ansible/c/b7bd7b0e354a4199621a0c9078c257f4cc15559e --- diff --git a/modules/sysadmin_guide/pages/coreos-cincinnati.adoc b/modules/sysadmin_guide/pages/coreos-cincinnati.adoc index a38fd10..965f232 100644 --- a/modules/sysadmin_guide/pages/coreos-cincinnati.adoc +++ b/modules/sysadmin_guide/pages/coreos-cincinnati.adoc @@ -45,26 +45,16 @@ Policy-engine:: === Build and deploy a new version -FCOS Cincinnati is built as container image directly from source, -referencing a pinned git commit. +FCOS Cincinnati is built as container image directly from source +from the `main` branch on the https://github.com/coreos/fedora-coreos-cincinnati +repo. -In order to build and deploy a new version, you will first have to find the -relevant commit (i.e. the latest on the `main` branch) at -https://github.com/coreos/fedora-coreos-cincinnati . +Here are the steps to trigger a new build: -Once you have identified the target commit, these are the steps to build -a new container image: - - * update the `fcos_cincinnati_git_sha` playbook variable in - `roles/openshift-apps/coreos-cincinnati/vars/staging.yml` - * update the `fcos_cincinnati_git_sha` playbook variable in - `roles/openshift-apps/coreos-cincinnati/vars/production.yml` - * commit and push the update to the `fedora-infra/ansible` repository * SSH to `batcave01.rdu3.fedoraproject.org` - * run `sudo rbac-playbook openshift-apps/coreos-cincinnati.yml` using - your FAS password and your second-factor OTP * schedule a new build by running `sudo rbac-playbook -t build openshift-apps/coreos-cincinnati.yml` + using your FAS password and your second-factor OTP * Wait for the coreos-cincinnati-img:latest tag to be updated == Things that could go wrong