检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
The deployment is based on Elastic Cloud Server (ECS). This approach is suitable for traditional software packages. To use container-based deployment, see Setting Up a CCE-based Code Development Pipeline.
Viedos Introduction Service Overview 06:13 Getting to Know CodeArts Operation Guide Setting Up a CCE-based Code Development Pipeline 05:01 Checking code, Building a software package and Deploying it to ECS Setting Up a CCE-based Code Development Pipeline 05:57 Developing, Building
Deploying Applications to ECS This section uses phoenix-sample-standalone as an example to describe how to deploy the build artifact to a host. For details about CCE-based deployment, see Deploying Applications to CCE. For details about how to prepare ECS, see Resource Planning.
Controller Node Architecture: X86 Network Model: VPC network Container CIDR Block: Auto select Buying a CCE Standard/Turbo Cluster Node Pay-per-use recommended Node Type: Elastic Cloud Server (VM) Specifications: 2 vCPUs | 8 GiB or above Container Engine: Docker OS: Public image >
This practice provides Cloud Container Engine (CCE) and Elastic Cloud Server (ECS) based deployment methods. Choose to prepare CCE or ECS resources to suite your needs.
For example, When using CodeArts Deploy, you need to deploy an application on Elastic Cloud Server (ECS). Therefore, you purchased a pay-per-use ECS. For details about the pay-per-use billing of ECS, see ECS Billing.
Release Repo Building with Maven, Uploading the Software Package, and Pushing the Image CodeArts Artifact Uploading Software Packages to Release Repos Uploading Components to Maven Repository CodeArts Deploy Creating a Tomcat Application Using CodeArts Deploy and Deploying It on an ECS
Table 1 Releasing Resources Resource Operation Guide ECS Deleting an ECS CCE Deleting a Pay-per-Use Cluster Parent topic: Implementation Procedure
Creates and executes a deployment application, obtains software package Z, and deploys it to an Elastic Cloud Server (ECS).
This document provides methods for CCE and ECS based deployments. Manage project tests Tester Billy creates a sprint test plan, designs test cases, and executes test cases as planned.
Executing a Test Case After developing story code and deploying applications to the test environment (see Deploying Applications to CCE or Deploying Applications to ECS), developer Chris sets the story status to Testing and the story handler to tester Billy.
following is an example policy containing actions of multiple services: { "Version": "1.1", "Statement": [ { "Action": [ "devcloud:*:listResourceDetail", "ecs
Replace Image Version of Docker-Compose Deployment File To ensure that the correct image can be pulled and then deployed on ECS, run shell commands to perform the following operations: Run sed commands to replace the values of parameters in docker-compose-standalone.yml with those
Implementation Procedure Preparations Managing Project Plans Developing Code Checking Code Building Images and Pushing Them to SWR Deploying Applications to CCE Deploying Applications to ECS Managing Project Tests Configuring Pipelines Releasing Resources Parent topic: Developing
