Functions
The following table describes the main functions of CodeArts Pipeline.
Function |
Description |
---|---|
Orchestrating pipelines |
You can manage and schedule jobs of building, code check, subpipeline, repositories, deployment, delayed execution, manual review, and API test. |
Adding, deleting, editing, and querying pipelines |
You can create, edit, delete pipelines and query execution status on the Web UI. You can go to the job details page to view its logs. |
Managing permissions |
You can configure project-level permissions for each role. You can configure permissions for each role and user in a pipeline to allow them to view, edit, execute, and delete the pipeline. |
Viewing pipeline execution records |
You can view the pipeline records in past 31 days. |
Configuring notifications |
You can configure whether to send internal messages and emails for pipeline events. |
Executing specific jobs |
You can execute specific jobs in a pipeline. |
Configuring parameters |
You can add custom parameters and set a value for the parameter when executing a pipeline, so that the job can use the value for execution. |
Executing jobs in serial or parallel mode |
You can execute jobs in a stage in serial or parallel mode as needed. |
The following table describes the main functions of policies.
Function |
Description |
---|---|
Managing policies |
You can manage policies at the tenant and project levels. |
Customizing rules |
You can customize rules based on extensions. |
Using policies |
You can use policies as pass conditions during task orchestration. |
Copying policies |
You can quickly create a policy by copying a tenant-level or project-level policy. In addition, you can copy a tenant-level policy as a project-level policy in a project. |
Inheriting policies |
You can inherit a tenant-level policy as a project-level policy under the tenant. |
The following table describes the main functions of extensions.
Function |
Description |
---|---|
System extensions |
The extension platform has multiple built-in extensions to meet DevOps requirements. |
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