From 0304dd7b9d3078488a68e36535f972b5fa0399b1 Mon Sep 17 00:00:00 2001 From: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com> Date: Wed, 7 Oct 2020 15:29:50 +0530 Subject: [PATCH] Add manual step about base-files The base-files package, depending on its branch name, generates the os distribution specific attributes. Since those attributes expect a certain set of infrastructure changes available (eg. new release's docker images), this step is classified to be executed manually. Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com> --- content/guides/apertis_release_process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/guides/apertis_release_process.md b/content/guides/apertis_release_process.md index 4d78f0277..f72d15687 100644 --- a/content/guides/apertis_release_process.md +++ b/content/guides/apertis_release_process.md @@ -124,13 +124,14 @@ Host images.apertis.org * Restart OBS to pick up the new reprepro entry (the magic is in `/etc/obs/BSConfig.apertis.pm`) * Clone and republish the OBS binary repositories * Restart the OBS schedulers - * Update and submit on OBS the base-files package * Update build suffix on OBS Project configuration (eg. `bv2019.0b<B_CNT>`, `bv2020dev0b<B_CNT>`). Please refer to section **Build Suffix** for more details about it * Add a directory for the release to the LAVA NFS path at: `/srv/images/public/lava/nfs/` on host images.apertis.org. The LAVA test jobs pick the kernel and initrd image from the release's directory path. Refer to the README for details * Update the [ci-package-builder](https://gitlab.apertis.org/infrastructure/ci-package-builder/) to target the next release * Update the [gitlab-rulez](https://gitlab.apertis.org/infrastructure/gitlab-rulez/) recipe to point to the new development release * Set the default development branch for all git projects * Set the protection settings onto all `apertis/*` branches, which were unprotected in the initial release steps +* Manually branch the [base-files](https://gitlab.apertis.org/pkg/target/base-files/) package, after the new docker images have been built. + * This step should automatically update the release specific attributes in the new package and auto propose the changes through a new merge request ## Build Suffix -- GitLab