检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 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
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 >
Replace Image Version of Docker-Compose Deployment File To ensure that the correct image can be pulled when the image is deployed on ECS, run the shell commands to perform the following operations: Run sed commands to replace the parameters in the docker-compose-standalone.yml file
Executing a Test Plan After developing story code and deploying applications on the test environment (see Step 6: Deploying an Application to CCE or Step 6: Deploying an Application to an ECS), the developer can set the story status to Resolved and set the story handler to the tester
Cloud Container Engine (CCE) 1 Elastic Cloud Server (ECS) 1 Parent topic: Developing an E-mall Project with CodeArts
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
ECS Log in to the ECS console. Locate the ECS to be deleted in the list, choose More > Delete, and follow the prompts to delete it. Released resources cannot be recovered. Exercise caution when performing these operations. Parent topic: Implementation Procedure
Creates and executes a deployment application, obtains software package Z, and deploys it to an Elastic Cloud Server (ECS).
Table 1 Preset applications Preset Application Description phoenix-cd-cce For deployment to CCE phoenix-sample-standalone For deployment to ECS phoenix-sample-predeploy For installing dependency tools on ECS This section uses the phoenix-cd-cce application as an example.
Purchasing and Configuring an ECS This section uses Elastic Cloud Server (ECS). You can also use your own Linux host that runs Ubuntu 16.04 OS. Buy an ECS. The following table lists mandatory configurations. You can also select other configurations as necessary.
following is an example policy containing actions of multiple services: { "Version": "1.1", "Statement": [ { "Action": [ "devcloud:*:listResourceDetail", "ecs
Elastic Cloud Server (ECS) Deploys software packages in a different way from CCE-based deployment.
Implementation Procedure Preparation Step 1: Managing Project Plans Step 2: Managing Project Configurations Step 3: Writing Code Step 4: Checking Code Step 5: Building Images and Pushing Them to SWR Step 6: Deploying an Application to CCE Step 6: Deploying an Application to an ECS
