Legacy Apsara DevOps (RDC) migration
This guide covers migrating from the legacy to the new version of Alibaba Cloud DevOps.
Dear customers,
Thank you for your support of the legacy Alibaba Cloud Apsara DevOps (https://rdc.aliyun.com/). To provide you with a more comprehensive service, richer features, and more responsive support, the legacy platform will stop accepting new subscriptions or renewals in April 2024 and will be retired on October 30, 2024. All features of the legacy version are now available on the new Apsara DevOps platform at https://devops.aliyun.com/.
While its core services remain free, the new Apsara DevOps provides an end-to-end R&D management service that covers the entire software lifecycle—from requirements and development to testing, deployment, operations, and metrics. It incorporates Alibaba's proven project management and engineering practices, offers enterprise-grade security, and features a value stream-based digital metrics system with end-to-end efficiency insights to help your organization accelerate its R&D digital transformation.
Advantages of the new version
Feature | Legacy Apsara DevOps | New Apsara DevOps |
Pricing | All features are charged on a per-user basis. | Core features are free for unlimited users. |
Project management | Limited capabilities | Rich capabilities: Standardize R&D processes with project templates; manage a hierarchy of epics, requirements, and original requests; automate workflows like user assignments and status transitions with automation rules; and enable integrated DevOps by linking to code, changes, and other objects. |
Codeup | Not supported | Supported |
Pipeline | Limited capabilities | Enhanced capabilities: Run builds in heterogeneous environments across multiple operating systems, accelerate builds with a build cache, use Pipeline as Code, and add custom steps for organization-specific scenarios. |
Application deployment | Limited capabilities | Rich capabilities: Host resources, orchestrate applications, manage environments, handle deployment and O&M, and support various development models. |
Artifact management | Limited artifact types | Manage multiple artifact types, including generic artifacts, Docker, Maven, npm, and NuGet. |
Efficiency report | Not supported | Supported |
OpenAPI | Not supported | Supported |
Permission controls | Basic controls | Fine-grained controls |
IP whitelist and behavior audit Other security features | Not supported | Supported |
User experience | Complex | Simplified |
Upgrade process
To begin the upgrade, contact technical support through our DingTalk group (ID: 36480001371) and submit the migration request form (download). Once your request is approved, we will schedule the migration with you. Assisted migration is available for the following modules:
Partial project management data
Partial artifact management data
Partial application and pipeline data
Significant system architecture differences between the legacy and new versions prevent a fully compatible data migration. After the migration, you must manually fine-tune configuration and parameters to achieve the desired results.
For details on the supported migration scope, see the data mapping section.
Data mapping
Project management data upgrade
Data migration from legacy Yunxiao projects to Projex is a one-time operation for existing organizations and is not followed by automatic synchronization. For data mapping details, see below.
Type | Legacy item | Migration mapping | Notes |
Member management | Organization member | Maps to | Synchronization is supported for new |
Program | Program | Maps to | If a |
Document | Document | Not supported for migration | |
RDC project data | Project name | Maps to project name |
|
Project background | Maps to project description | ||
Project goal | Supported for migration | ||
Project creation time and update time | Maps to creation time | Update time is not migrated. | |
Project icon | Maps to |
| |
Project completion status | Maps to |
| |
Project visibility | Maps to project visibility | ||
Project type | Supported for migration | ||
Project announcement | Supported for migration | ||
Parent project | Maps to a | ||
Associated program | Maps to the associated program | ||
Planned start/end time | Maps to project start and end time | ||
Actual start/end time | Supported for migration | ||
Progress | Supported for migration | ||
Lifecycle | Supported for migration | ||
Health status | Supported for migration | ||
Project member | Maps to project member | ||
Tag | Maps to | ||
Version | Maps to | Parent-child version relationships are not supported. | |
Module | Maps to a | ||
Milestone | Maps to | Module linking is not supported. | |
Iteration | Maps to | ||
Role | Administrator | Maps to the Project Administrator role | |
Participant | Maps to the Project Participant role | ||
Other custom roles | Maps to custom project roles | ||
Permission | Admin permission | Maps to all project permissions | |
Standard permission | Maps to all permissions except for project settings management. | ||
Settings | Work item type | Maps to a subtype of the corresponding Requirement, Task, or Defect parent type. | |
Workflow | Maps to the | ||
Field | See the field mapping table. | ||
Template | Supported for migration | ||
RDC work item data | Title | Maps to title | |
Description | Maps to description | ||
Work item type | Maps to | ||
Status | Maps to status | ||
Creation time and update time | Maps to creation time | Update time is not migrated. | |
Creator | Maps to creator | ||
Assignee | Maps to | ||
Watcher | Maps to | ||
Verifier | Maps to | ||
Priority | Maps to | ||
Severity | Maps to | ||
Owning project | Maps to owning project | ||
Linked project | Maps to shared project | ||
Iteration | Maps to | ||
Module | Maps to a multi-select | ||
Version | Maps to | ||
Tag | Maps to | ||
Custom field | Maps to | ||
Sub-item | Maps to | ||
Linked item | Maps to | ||
Comment | Maps to | ||
Attachment | Maps to | ||
Activity log | Maps to | The activity log is converted to plain text entries. | |
Field type mapping | Text | Maps to | |
Long text | Maps to | ||
Integer | Maps to integer | ||
Float | Maps to | ||
Single-select list | Maps to | ||
Multi-select list | Maps to | ||
Date | Maps to date | ||
Boolean | Maps to | ||
Fuzzy search | Maps to text | ||
Object (User) | Maps to single-user selection | ||
Dynamic single-select list | Maps to text | ||
Dynamic multi-select list | Maps to text | ||
Information display | Maps to text | You can configure this as read-only using the field settings in | |
Project test service data | Not supported for migration | ||
Test case data | Not supported for migration | ||
Test plan | Not supported for migration |
Artifact management data upgrade
Migrating data from a legacy Apsara DevOps Maven private repository to Packages is a one-time operation with no subsequent automatic synchronization. The data mapping is as follows:
Legacy RDC item | Migration mapping | Notes |
Maven release repository | Migrates to a Maven repository with the same name and a | Packages lets you create private Maven repositories and set storage policies. After migration, the repository is assigned a new address and credentials. You must then update your dependency file configuration. |
Maven snapshot repository | Migrates to a Maven repository with the same name and a | |
Maven artifact | All artifacts are migrated. | This is a one-time migration. Artifacts added after the migration are not automatically synchronized. |
Remote repository proxy | Migration not supported. | You must configure the proxy manually. |
We recommend manually migrating data from your legacy Codeup Helm private repository to Alibaba Cloud ACR Helm charts.
Application and pipeline data upgrade
Legacy data from Yunxiao pipelines is migrated to Flow, and data from Yunxiao applications is migrated to AppStack. This migration covers only basic data mapping and transfer, and may not fully preserve your processes. After migration, you must manually adjust the process configuration and test your application to verify that it runs as expected. The data mapping is as follows:
Type | Legacy RDC item | Target module | Data mapping | Notes |
Organization settings | RAM authorization management | AppStack - Global Settings | service connection | |
Machine Management | AppStack - Resource Pool | resource pool - host cluster | ||
Container Service Account | AppStack - Resource Pool | resource pool - Kubernetes cluster | ||
Build Image Management | - | Not supported for migration | ||
Application basic information | Application name | AppStack - Application | Application name | |
Application description | Application description | |||
Application members | Application members | |||
Operation history | Not supported for migration | |||
Application deployment configuration | Kubernetes deployment | AppStack - Application Orchestration | application Kubernetes orchestration | |
Alibaba Cloud Container Service for Swarm cluster | Not supported for migration | |||
EDAS deployment | Not supported for migration | You can manually configure an EDAS step in Flow. | ||
Script deployment | application host orchestration | |||
Application environment | Environment name | AppStack - Environment Management | Environment Display Name | |
Environment level | environment tag | |||
deployment mode | deployment mode | |||
deployment strategy | Not supported for migration | Select the deployment strategy when deploying to an environment. It is then automatically inherited for subsequent deployments. | ||
Deployment history | Not supported for migration | |||
feature branch | change | AppStack - Change Development Process | Not supported for migration | Historical change data is not migrated. Use the AppStack Change feature to manage new changes. |
secret | common variable group | Flow - Common Variable Group | common variable group | |
version | Package version | AppStack - Application Version | Not supported for migration | Historical version data is not migrated. Use the AppStack Application Version feature to manage new versions. |
Personal certificate | Certificate name | Flow - Service Connection | Certificate name | Each certificate is automatically migrated to a dedicated service connection. Select the appropriate service connection during configuration. |
Username | Username | |||
password/token | password/token | |||
Visibility Scope | Service Connection Member Permissions | |||
Pipeline basic information | Name | Flow - Pipeline Basic Information | Pipeline Name | |
Pipeline ID | Pipeline ID | |||
Project | Not supported for migration | |||
Associated application | Association with AppStack application | |||
Disable multiple instances | Not supported for migration | |||
Pipeline member permissions | First administrator | Flow - Pipeline Member | pipeline owner, with all permissions | |
Other administrators | Pipeline member, with all permissions | |||
All organization members | Pipeline member, with run permission | |||
Pipeline code source | Code repository | Flow - Pipeline Code Source | Code repository | |
Branch | Default branch | |||
Dynamic branch | Not supported for migration | |||
Credential type | Credential type | |||
personal certificate | service connection | |||
Alias | Not supported for migration | |||
Pipeline process configuration | job | Flow - Process Configuration | job | |
step | step | |||
plugin | plugin | |||
Pipeline environment variables | PIPELINE_ID | Flow - Environment Variables | PIPELINE_ID | You must replace these variables with their corresponding system variables in Flow. Flow also supports additional system and custom variables. For more information, see Environment Variable Source. |
BUILD_NUMBER | BUILD_NUMBER | |||
EMPLOYEE_ID | BUILD_EXECUTOR | |||
CODE_INFO | CI_COMMIT_REF_NAME (The branch or tag name of the code source) | |||
VERSION | Not supported for migration | |||
PACKAGES | Not supported for migration | |||
Pipeline trigger method | automatic trigger | Flow - Trigger Method | automatic trigger | |
Pipeline run | manual trigger | manual trigger | ||
scheduled trigger | scheduled trigger | |||
history | Flow - Pipeline Run | Not supported for migration |
Project: cross-organization collaboration data upgrade
Cross-organization project collaboration allows projects in an Apsara DevOps RDC organization to share data, such as basic project information, project members, and work items (requirements and defects), with select projects on the Alibaba Group internal collaboration platform. If you do not use this feature, you can skip this section.
The new platform (https://project.alibaba.com) now supports cross-enterprise project collaboration. For questions about the new platform or data upgrade requests, join the DingTalk group (77450015632) to contact technical support. For more information, see New cross-enterprise collaboration platform.
Upgrade impact
Due to major upgrades to the system architecture and model, migrated data is not fully compatible with the new version. After the migration, you must manually tune the configuration and parameters to ensure the expected performance and functionality.
Incremental data upgrades are not supported. To prevent data inconsistencies, we strongly recommend that you stop writing new data to the legacy platform after the upgrade and transition all operations to the new platform.
FAQ
1. What are the advantages of the new version?
Project collaboration:
Automate workflows with flexible automation rules to transition statuses, assign items, send reminders, synchronize parent-child items, link development objects, and integrate with third-party platforms. For more information, see automation rules.
Facilitates seamless, cross-functional collaboration among business, product, and engineering teams. This layered model allows each team to focus on their core tasks. For more information, see Layered collaboration for business, product, and engineering.
Provides a highly customizable workbench.
Standardize your development processes. Use the project template synchronization feature to ensure all projects adhere to your team's defined delivery workflows. For more information, see Project template sync configuration.
Artifact repository:
Create multiple private repository instances.
Manage multiple artifact types, including Maven, npm, and generic artifacts.
Application and pipeline
Enables a continuous delivery model for application changes.
Provides tools for application deployment orchestration, environment management, and operations.
Use private build clusters to run pipeline builds on your self-hosted machines.
Use pipeline as code to orchestrate your pipelines with YAML.