Migrating Alauda DevOps to Alauda DevOps (Next-Gen)
This guide details the upgrade strategy and procedures for Alauda DevOps to Alauda DevOps (Next-Gen), Suitable for ACP upgrade scenarios:
v3.18-->v4.0v3.18-->v4.1v4.0-->v4.1
TOC
Prerequisites
Upgrade Alauda DevOps to v3.20
Before migration, ensure that Alauda DevOps is upgraded to version v3.20. This step is required for compatibility and successful migration to Alauda DevOps (Next-Gen). Please refer to Upgrading Alauda DevOps to v3.20
Migrating Alauda DevOps
Starting from ACP v4.1, the following Alauda DevOps v3 operators will no longer be maintained. Therefore, migrating these operators is required.
Download the Operator
- Download the following versions of the Operators separately or in bulk based on templates from the Alauda customer portal.
The .z in version numbers indicates the latest available patch version for that minor release. During upgrade, you should always use the latest patch version to benefit from the most recent security updates and bug fixes.
- Navigate to the CLI Tools section in the Alauda Customer Portal and download the
violettool to upload Operators toACP. For specific operation steps, refer to
Migrating Alauda DevOps
Please refer to the following documents for migrating each operator:
- Migrating Alauda DevOps Pipelines
- Migrating Alauda Build of Gitlab
- Migrating Alauda Build of Harbor
- Migrating Alauda Build of SonarQube
- Migrating Alauda Build of Nexus
Next Steps
You have now completed the migration from Alauda DevOps to Alauda DevOps (Next-Gen). In Alauda DevOps (Next-Gen), if you want to use the updated version for each Operator, you can further learn how to upgrade to the updated version in each operator's documentation.
Important Restriction
If you need to continue using the Build and Release features from Alauda DevOps v3, you must maintain Alauda DevOps Pipelines at version v4.0.z.
Prohibited Actions
Do NOT upgrade Alauda DevOps Pipelines beyond v4.0.z under any circumstances. Upgrading to versions above v4.0.z will cause irreversible compatibility issues with katanomi, potentially breaking existing Build and Release pipelines.