Overview

Before referencing a builds Task or releases Stage, you need to store the Task or stage definition file in a specific space, namely “source”. The essence of source is a code repository. Sources are divided into platform sources, which are provided by the platform, and user-defined sources.

The platform has integrated platform sources by default, so no additional settings are required., while custom sources need to be created as needed. Source management means the management of custom sources.

Platform Sources

The tasks and stages provided by the platform by default come from the platform sources. All project members can directly use platform tasks and stages when creating pipelines.

Custom Sources

If more tasks or stages need to be used, both administrators and project members can write configuration files for tasks or stages and store them in the code repository. Administrators need to create custom sources based on the code repository and complete the allocation.

If the platform administrator has assigned a source to a project, all operations, development, or testing personnel in the namespaces under the project can directly use the source. If the project administrator creates a source separately, the source needs to be assigned to the corresponding namespace before the namespace users can use it.

Note:

• The dashed box in the figure represents optional operations.

• Path 1 indicates that project members can only reference custom tasks and stages.

• Path 2 indicates that project members can not only reference custom tasks and stages, but also directly edit the configuration files of custom tasks and stages in the platform. After modifying the files, the release pipelines that reference custom tasks or stages will automatically apply the new configuration.

• To modify custom tasks or stages, please refer to the “Code Management > Custom Tasks or Stages” section in the DevOps Help documentation.