- Service Overview
- Billing
- Getting Started
-
User Guide
- Preparations
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
Best Practices
- Best Practices Summary
-
Using CodeArts to Manage an e-Mall Development Project
- Overview
- Resource Planning
- Process
-
Implementation Procedure
- Preparation
- Step 1: Managing Project Plans
- Step 2: Managing Project Configurations
- Step 3: Writing Code
- Step 4: Checking Code
- Step 5: Building an Application
- Step 6: Deploying an Application (CCE)
- Step 6: Deploying an Application (ECS)
- Step 7: Managing Project Tests
- Step 8: Configuring a Pipeline for Continuous Delivery
- Releasing Resources
-
FAQs
-
General
- How Do I Collect or Archive Project Information Locally After a CodeArts Project Is Complete?
- Why Can't an IAM User View Any CodeArts Projects After Login?
- How Do I View All CodeArts Projects and Members Under My Account as Administrator?
- Will the Tasks Created by a Project Member Be Deleted After the Member Leaves the Project?
- Will a New User with the Same Name as a Deleted User Inherit Their Permissions and Tasks?
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
General
- Videos
- General Reference
Show all
Copied.
Execution Duration
CodeArts provides execution duration extension for resource-consuming pipeline tasks.
Billing Mode |
Yearly/Monthly |
---|---|
Scenario |
If the execution duration of resource-consuming pipeline tasks in your CodeArts package does not meet your requirements, purchase execution duration extension for resource-consuming pipeline tasks. |
Resource Specifications |
Duration (min/month) |
Purchase Limits |
|
Billing Formula |
Unit price × Duration × Purchased duration |
Billing Cycle |
Determined by the purchased duration (GMT+08:00). The billing cycle starts from the time you activate or renew your pipeline execution duration extension (precise to seconds), and ends at 23:59:59 on the expiration day. For example, if you purchased pipeline execution duration extension for one month on Mar 08, 2023, 15:50:04, the billing cycle is from Mar 08, 2023, 15:50:04 to Apr 08, 2023, 23:59:59. |
Configuration Change |
Supported. The system will calculate the change fee according to the following rules:
For more information, see Pricing of a Changed Specification. |
Impact of Expiration |
The pipeline execution duration extension will become invalid if not renewed before expiration. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot