Moving from Allure TestOps Server to Allure TestOps Cloud

Before continuing, please be mindful that migration is a very time-consuming process, especially if you have large amounts of data. Plan your downtime accordingly and feel free to contact our support team at any point if you have any questions.

The process of moving to Allure TestOps Cloud includes the following steps:

1. Creating an Allure TestOps Cloud instance.
2. Creating a ticket in our support system.
3. Deleting test artifacts so that the overall storage usage does not exceed Cloud limits.
4. Creating data archives and sending them to our support team.

Creating Allure TestOps Cloud instance

To create an instance to which you will be migrating, navigate to the Start Free Trial page and fill out the form. After the instance was created, go to Administration → License → Manage licenses and provide payment information to purchase a license.

Creating support ticket

To initiate the migration, you need to contact our support team via a support ticket. This ticket will be used for communication purposes during the entire migration process.

1. Go to help.qameta.io and create a new Support ticket.

2. As the subject, use the following template:

   Migration to SaaS <instance_name>.testops.cloud for <your_company_name>

   where

   • <instance_name> is the domain name you used when registering the Cloud instance
   • <your_company_name> is the name of your company

3. Specify the version of Allure TestOps Server you are currently using and any additional details in the ticket message.

Deleting test artifacts

If the total data amount of your Allure TestOps Server instance exceeds 60 GB, you need to delete some of the data to fit within that limit.

Usually, the largest part of Allure TestOps data are test artifacts, which can be deleted using clean-up rules. You can configure the rules to only keep the artifacts you need the most.

As an example, to keep only test artifacts no older than 2 days:

1. Go to Administration → Clean up policies to create global clean-up rules.

2. Click the + Create button to create rules for all targets and result statuses (15 rules in total). Specify 48 hours as the clean delay.

   Clean-up rules

   Target	Test result status	Clean delay
   Attachment	Failed	48
   Attachment	Broken	48
   Attachment	Passed	48
   Attachment	Skipped	48
   Attachment	Unknown	48
   Scenario	Failed	48
   Scenario	Broken	48
   Scenario	Passed	48
   Scenario	Skipped	48
   Scenario	Unknown	48
   Fixture	Failed	48
   Fixture	Broken	48
   Fixture	Passed	48
   Fixture	Skipped	48
   Fixture	Unknown	48

Once you have created the clean-up rules, you can manually trigger the cleanup job so you don't have to wait for the next scheduled run. To do so, you need to make a few API requests.

1. Go to <testops>/swagger-ui.html, where <testops> is the base URL of your Allure TestOps Server instance.
2. Find the cleanup-controller category.
3. Click on /cleanup/scheduler/cleaner_schema_global and then on Try it out. Wait for the request to finish.
4. Click on /cleanup/scheduler/cleaner_schema_project and then on Try it out. Wait for the request to finish.
5. Click on /cleanup/scheduler/blob_remove_task and then on Try it out. Wait for the request to finish.

If you have a large amount of test artifacts, some of the requests may show an error message. You can safely ignore it, as it does not affect the cleanup process.

The cleanup job may take some time to complete. You can monitor the progress by executing the following SQL query against the testops service database:

SELECT COUNT(*) FROM blob_remove_task;

Once the query returns 0 (no cleanup tasks left to process), you can proceed to the next step.

Creating data archives

The instructions are valid only for Allure TestOps version 5.

1. Stop all traffic to your Allure TestOps Server instance by stopping the Allure TestOps service or your load balancer, or disabling the routes in your ingress controller.

2. Create a dump of the testops service database.

   pg_dump -U [POSTGRESQL_USER] testops > testops-backup.sql
   

3. Download all files from the test artifacts storage using S3cmd or similar tool.

4. Create one or more archives with the database dump and files from the artifacts storage. Encrypt the archives with a strong password.

5. Upload the archives to a server so our support team will be able to access them.

6. Message the archives links and passwords to our support team using the ticket you created previously.

After our support team receives the archives, the data import process will take up to 24 hours. Once the data is imported and your Allure TestOps Cloud instance is ready to be used, we will inform you using the same support ticket.