Overview

Extensions

Larger enterprises tend to have their own pipeline tool chains. However, after cloud migration, assets such as self-built CI/CD tools and open-source tools cannot be inherited and end up wasted. CodeArts Pipeline solves this by allowing enterprises to quickly connect existing tools to the Pipeline service or develop their own extensions through the extension platform. CodeArts Pipeline provides a visualized, low-code, and open extension market to adapt to service requirements. CodeArts Pipeline has a collection of built-in extensions covering build, check, deployment, and test. You can use these extensions for pipeline orchestration.

Extensions can be used by tenants. An extension is a step in a pipeline job. It is the minimum running unit defined by JSON Schema and contains input parameters, service execution logic, and output content.

Accessing the Extension List

• Entry 1: Log in to CodeArts and choose Services > Extensions from the top navigation bar.
• Entry 2: Go to the pipeline list of a project to create or edit a pipeline. When adding a job to a pipeline, click More Extensions in the upper right corner.

The extension page displays all available extensions. You can click the card of an extension to view details.

Scenarios

• You can use official tools to develop extensions. CodeArts Pipeline allows you to compile service scripts in mainstream languages, such as Shell, Node.js, Python, and Java. For details, see Official Tools. Some basic extensions can be used together with custom executors to provide more execution modes.
• You can use official extensions (such as Kubernetes Release, CAE Release) to connect to different cloud services.
• You can also customize extensions to connect to third-party CI/CD tools.