Code Pipeline is committed to providing an open and user\-friendly enterprise\-grade CI/CD platform to help enterprises deliver business value with high quality and efficiency. This document provides a detailed introduction to the features currently supported by Code Pipeline. ## Overview Introduce the product definition, usage workflow, and commonly used feature entry points of Code Pipeline to help you quickly understand the product. * Demonstrate the Code Pipeline workflow and provide a step\-by\-step guide for beginners to help you quickly get started with Code Pipeline. * Workspace: Provides an entry point for creating a workspace and supports quick navigation to the 10 most recently used workspaces. ## Workspace A workspace is a virtual working environment. Each workspace operates independently, allowing enterprises to divide different projects among separate workspaces for management. * Workspace lifecycle management: create, view, edit, copy, and delete workspaces. * Workspace permissions: Supports setting the workspace visibility scope for permission management. ## Code source The code source is one of the pipeline's input sources. Code source manages your repository URL and token information. * By creating a code source, you can connect to various types of code repositories, including Gitee, GitLab, GitHub, Codeup, Gerrit, and more. * Supports viewing code sources, checking code source connectivity, editing, and deleting code sources. ## Pipeline The pipeline is the carrier for Code Pipeline, enabling continuous delivery throughout the entire process from development to production by means of build automation, integration automation, validation automation, and deployment automation. |Features |Description | |---|---| |Pipeline templates |Provides commonly used pipeline templates for Go, Node.js, Java, and Python. | |Pipeline management |The pipeline is the vehicle for continuous delivery enabled by Code Pipeline, completing the process from development to launch through build automation, integration automation, validation automation, and deployment automation.

* Pipeline full lifecycle management: including creating, viewing, editing, copying, and deleting pipelines, among other actions.

* Save pipelines with incomplete configuration to the draft box

* Run a pipeline: Specify a branch, tag, or commit ID to run the pipeline.

* Terminate the pipeline: You can terminate the pipeline at any time during its execution.

* Failure retry: When a pipeline run fails, you can retry from the failed task.

* Real\-time logs: Provide run logs for each step in the pipeline, allowing users to track the pipeline's execution.

* Pipeline run details: View detailed information about pipeline runs, including the execution process and results, configuration information (such as basic information, environment variables, cache directory, and notifications), and detailed run information for each task or step (including run results, run logs, configuration information, and artifacts).

* Pipeline run history: Displays the run records for each pipeline to facilitate traceability.

* Pipeline notification records: Displays the notification records for each pipeline, including the pipeline run ID, the event that triggered the notification, notification details, trigger time, and more. | |Pipeline configuration |Configure and orchestrate pipelines, and define your automated delivery process.

* Configure code source: Configure the code repository and branch to be pulled by the pipeline.

* Build environment: Supports public resource pool (system\-provided public build cluster) and private resource pool (user\-defined private build cluster).

* Pipeline trigger rules include manual trigger, Webhook trigger, and scheduled trigger.

* Supports configuring automatic invalidation rules for Webhook and scheduled triggers to prevent frequent trigger failures in abnormal pipelines.

* Graphical orchestration: Provides graphical orchestration capabilities, supporting drag\-and\-drop for a three\-layer structure: stages, tasks, and steps. By orchestrating pipelines, you can organically connect tasks across each stage—such as testing, building, and deploying—to define your automated delivery process.

* Skip failed steps: Supports forcibly skipping failed steps and continuing pipeline execution, to meet requirements where the pipeline must proceed despite step failures.

* Environment variables: Each step in the pipeline can use environment variables as dynamic parameters, increasing the pipeline's flexibility. Currently supports dynamic, private, general, predefined, and custom environment variables.

* Cache directory: Configure the cache directory for build tasks. During the build process, dependencies that need to be downloaded are cached in the project path, improving the efficiency of subsequent builds. Currently supports preset or custom cache directory.

* Pipeline notification reminders: Pipeline notifications can be delivered via in\-app messages, SMS, email, Webhook, or Feishu bot, enabling you to quickly learn the results of build and deployment.

* Task Notification: Supports sending task\-level messages via Webhook and Feishu bot to help you stay informed about task updates. | ## Application delivery An application\-centric cloud\-native application delivery platform that provides one\-stop, out\-of\-the\-box capabilities such as application access, configuration management, application release, and more, helping enterprises establish a comprehensive Code Pipeline solution. |Features |Description | |---|---| |Member management |Provides dedicated member and permission management for application delivery: supports adding, modifying, and deleting application members, assigning preset role permissions to members, and supports multi\-role collaboration during application delivery. | |Application management |Provide application\-centric lifecycle management capabilities.

* K8s YAML application management: Supports defining applications using native K8s YAML, enabling application creation, quick application onboarding, editing basic application information, and application deletion. This feature is designed for developers who are familiar with K8s.

* OAM application management: OAM (Open Application Model) applications are cloud\-native applications with a low barrier to entry, designed to reduce the difficulty of application development and operations through standardized management and deployment. Provides features such as creating applications, quickly onboarding applications, modifying basic application information, and deleting applications for OAM, helping lower the barrier to entry for Kubernetes. | ||| ||| |Environment management |Perform full lifecycle management of Kubernetes environment instances for different categories (development, testing, staging, and production), including create, edit, and delete actions. | |Deployment and maintenance |Deploy the application to the target environment instance and perform operations and maintenance for the environment.

* Deployment strategies: Supports native deployment and phased release.

* Manually initiate deployment, trigger via workflow, or trigger via pipeline.

* Observing the deployment process: During the environment deployment process, you can view deployment details, view real\-time Pod logs, cancel the deployment, and more.

* Deployment records: Supports tracking environment deployment records, rapid rollback, and more. | |External integrations |Integrate external image repository services into application delivery Supports adding, editing, and deleting external services. | |Application template |Provide component templates and O&M plugin templates to help quickly generate OAM applications.

* Component templates: Enable quick generation of components for OAM applications. Preconfigures commonly used component templates and supports operations and maintenance personnel in customizing component templates for OAM applications.

* Operation and maintenance plugin templates: Help enhance the extensibility of OAM applications during operation. Commonly used plugin templates are preconfigured, and operations and maintenance personnel can customize plugin templates for OAM applications. | ## Resource management Used for unified management of deploy resources required for deploy tasks and build resources required for build tasks. |Features |Description | |---|---| |Deployment resource management |Used to manage the actual deployment locations of applications, such as Kubernetes clusters, cloud servers, virtual machines, physical machines, and more.

* Supports access to multiple types of deployment resources, including VKE clusters and custom clusters (by specifying a kubeconfig file).

* Supports viewing, editing, and deleting deployment resources.

* Supports controlling which workspaces can view deploy resources. | |Build resource management |An environment used for managing and running build tasks.

* Supports public resource pools (system\-provided build clusters) and private resource pools (user\-defined build clusters).

* Private resource pool lifecycle management: Supports creating, editing, disabling, and deleting private resource pools. | ## Template marketplace Includes commonly used pipeline step templates and provides a custom steps feature to meet users' personalized build and deployment needs. |Features |Description | |---|---| |Step template |Provide ready\-to\-use step templates for pipelines to meet enterprise requirements for daily build, test, deploy, and more tasks.

* SonarQube code scanning: Supports integration with the SonarQube code analysis platform to enable rapid code detection and effective code quality management.

* Unit testing: Supports unit testing for Java Maven, Java Gradle, Python, and Go.

* Command execution: Supports Bash command execution.

* Manual checkpoint: The pipeline pauses and waits for human intervention, for example during manual testing or security review.

* Compilation and build: Supports compilation and build for Java (Maven and Gradle), Python, Go, and Node.js.

* Package and push images to a custom repository: Package the image and push it to a third\-party repository. Support packaging of multi\-architecture images and skipping certificate verification.

* Package and push container images to the image repository: Package the container image and push it to the image repository. Support packaging multi\-architecture images and skipping certificate verification.

* Kubernetes image upgrade: Supports upgrading images for applications on the Kubernetes cluster.

* Kubernetes rolling update: Supports batch rolling updates of Deployments on a Kubernetes cluster by instance.

* Create new Kubernetes applications, tasks, and more using YAML files

* Custom environment command execution

Supports using a custom environment to execute commands, suitable for scenarios where built\-in tasks do not meet user requirements. | |Custom steps |Custom steps are used to extend the capabilities of the pipeline to meet the personalized build and deployment needs of enterprises. For example, tools or commands that the team is proficient with can be packaged as custom steps, making it easier for other projects and team members to quickly reuse them.

* Supports creating, updating, enabling, and disabling custom steps, and viewing pipelines associated with custom steps. |