From 2d8cbb11ed8b25b399134153b305e0847df36d0e Mon Sep 17 00:00:00 2001 From: Giovanni Toraldo <71768+gionn@users.noreply.github.com> Date: Thu, 7 Mar 2024 11:24:34 +0100 Subject: [PATCH] OPSEXP-2510 Update release docs (#808) --- docs/developer-guide.md | 29 ++--------------------------- 1 file changed, 2 insertions(+), 27 deletions(-) diff --git a/docs/developer-guide.md b/docs/developer-guide.md index 19e8ea11b..6708e4c94 100644 --- a/docs/developer-guide.md +++ b/docs/developer-guide.md @@ -151,34 +151,9 @@ doc](./README.md#versioning) Follow this quick checklist: * copy the versions inside the group_vars/all.yml to a new X.X.N-extra-vars.yml -* run updatecli against the latest and supported versions (one for each extra-vars file) - * e.g. `updatecli apply --config scripts/updatecli/updatecli_config.tpl --values scripts/updatecli/updatecli_base.yml --values scripts/updatecli/updatecli_acs23.yml` +* run [updatecli workflow](https://github.com/Alfresco/alfresco-ansible-deployment/actions/workflows/updatecli.yml) * ensure that the [tables in the main readme](README.md) has been updated -* ensure that AMI id for the root molecule tests are not outdated (e.g. [default suite](../molecule/default/vars-rhel8.yml)) - -### Bumping ACS version via updatecli - -This repo provide experimental support for updatecli to keep ACS components -versions in sync with the latest ACS releases. Configurations files are in the -`scripts/updatecli` folder. - -The `updatecli_config.tpl` file provides the main pipeline definition and there -are multiple values files depending on which acs major version we want to check -for any new minor release. - -Run updatecli with: - -```bash -updatecli apply --config scripts/updatecli/updatecli_config.tpl --values scripts/updatecli/updatecli_base.yml --values scripts/updatecli/updatecli_acsXX.yml -``` - -Once the command completes successfully, you will find the target file -automatically modified with the latest available versions: - -* `groups_vars/all.yml` - -Commit and push them on a new `next/acs-XX` branch, if you are starting to the the new pre-release versions. -If you are at release time, just raise a PR to merge in `master`. +* ensure that AMI id for the root molecule tests are not too outdated (e.g. [default suite](../molecule/default/)) ### Tag and release