Upgrading to release 26.1.1

The following actions for the on-prem deployments are very important and cannot be omitted. Skipping this will lead to inability of the application to start.

Before the upgrade

Size of the table test_fixture_result_children

Before performing the upgrade to Allure TestOps 26.1.1 you need to check the size of the database table test_fixture_result_children as follows.

1. Connect to Allure TestOps database.
2. Run the command select pg_size_pretty(pg_total_relation_size('test_fixture_result_children'));
3. Check the returned size.

If the returned size of the table is less than 1 Gbyte, then proceed to the config update as described here, otherwise, please do the following.

If test_fixture_result_children more than 1 Gbyte

If the size of database table test_fixture_result_children is more than 1 Gbyte, DO NOT perform the upgrade but plan the upgrade as you will need to stop any workload to the system.

1. Stop all workload to Allure TestOps.
2. Perform a full truncate of the table test_fixture_result_children: truncate table test_fixture_result_children;
   • This is a safe operation, it does not lead to the deletion of any important data if performed without workload.
3. Create primary key for the table test_fixture_result_children as follows

alter table test_fixture_result_children
        add constraint pk_test_fixture_result_children primary key (test_fixture_result_id, uuid);

With the truncated table this process will be completed immediately.

As soon as the operation has been completed, you can proceed to the next step of the configuration update.

Config update

Helm chart

1. Helm chart needs to be updated to the most recent version.
2. Parameter maxS3Concurrency has been replaced by the following 3 parameters.
   1. maxS3Connections, see here
   2. coreS3Threads, see here
   3. maxS3Threads, see here
3. Parameters need to be added with the default values as these are shown in values.yaml template. We do not recommend alteration of the default values unless it's explicitly recommended by Allure TestOps support team.

After the configuration has been updated, you can upgrade the release as usual.

Docker compose config

Set TESTOPS_TASKEXECUTOR_COREPOOLSIZE in .env file to the value 50.

Set RELEASE_TO_DEPLOY=26.1.1

Then execute

docker compose down && docker compose up -d

Linux packages

1. Open Allure TestOps config file /opt/testops/conf/testosp.conf
2. Locate parameter ALLURE_TASKEXECUTOR_COREPOOLSIZE
   1. set it to 50
3. Locate ALLURE_BLOBSTORAGE_MAXCONCURRENCY
   1. set it to 100
4. Save file
5. Restart the service (sudo systemctl restart testops).
6. Perform the release upgrade as usual.