Help Center/ CodeArts Pipeline/ Service Overview/ What Is CodeArts Pipeline?
Updated on 2023-11-28 GMT+08:00
View PDF

What Is CodeArts Pipeline?

CodeArts Pipeline provides visualized continuous integration and continuous delivery (CI/CD) pipelines that can be orchestrated. It helps enterprises quickly realize continuous delivery and efficient automation in DevOps, shortens the time to market (TTM) of applications, and improves R&D efficiency.

This service is essentially a visualized and automated task scheduling platform. It needs to be used together with automation tasks of services such as CodeArts Build, CodeArts Check, CodeArts TestPlan, and CodeArts Deploy in software development pipeline. You can orchestrate these automation tasks based on your requirements, such as application deployment in the development, test, or production environment. After the tasks are configured, they can be automatically triggered, scheduled, and executed to avoid frequent and inefficient manual operations.

CodeArts Pipeline provides the following functions:

  • Allows you to add, delete, edit, and query pipeline tasks in a visualized manner.
  • Supports permissions control based on accounts, roles, and pipeline operations.
  • Supports management and scheduling of multiple task types, such as build, code check, subpipeline, repository management, deployment, extension type, API Test, and pipeline control (delayed execution and manual review).
  • Allows you to add, delete, and edit pipeline stages as required.
  • Allows you to configure serial and parallel execution of managed tasks in each pipeline stage.
  • Allows you to configure parameters for pipeline execution.
  • Allows you to select and execute some tasks in a pipeline.
  • Allows you to view pipeline execution records.
  • Allows you to configure one or more of the following execution plans: continuous integration, merge requests, and scheduled execution. Once conditions specified in one execution plan are met, a pipeline can be automatically triggered and executed.
  • Supports pipeline event notifications by message and email.
  • Allows you to customize extensions for more pipeline execution functions.
  • Allows you to create rules and policies for unified management and control of pipeline quality.
  • Supports microservice-based DevOps lightweight change mode.
  • Supports open-source dependency parsing based on source code and vulnerability interception.

What Are Rules/Policies?

CodeArts Pipeline allows you to manage pass conditions in pipeline stages based on rules and policies. You can create appropriate rules using extensions, set the threshold comparison conditions, reference the conditions in policies, and apply them in pass conditions. A policy is a set of rules. CodeArts Pipeline supports hierarchical policy management by tenant or project, facilitating efficient project management and ensuring product delivery quality.

What Are Extensions?

CodeArts Pipeline provides a series of extensions for you to use during task orchestration. You will be able to customize pipeline extensions to expand the business scope using automatic pipeline scheduling capabilities.

What Are Microservices?

A microservice is a software governance architecture. A large-scale complex software project consists of one or more microservices. Microservices in the system are loosely coupled. You can develop, build, verify, deploy, and roll out microservices parallelly. Microservices have the following advantages:

  • Clear boundaries: Each microservice focuses only on one function. It is relatively easy to develop and maintain a single microservice.
  • Independent deployment: A single microservice is independently deployed and updated, ensuring 24/7 service.
  • Diversified technologies: Microservices can be implemented using different technology stacks. Different services communicate with each other through RESTful APIs. Each service can be implemented using different technology frameworks and vaults.

What Are Changes?

A change is an R&D delivery activity. Project R&D requirements can be met and vulnerabilities can be fixed using changes. One change belongs to only one microservice.

A change has its own release lifecycle, including developing, to release, releasing, and released. One or more changes can be released through the change pipeline for quick project delivery. In addition, pass conditions and review processes can be added to changes for quality control.