Overview

Before referencing Builds tasks or Releases stages, the configuration files of tasks or stages need to be stored in a specific space, namely, the Source. Depending on the provider of the source, there are platform sources provided by the platform and custom sources used by users.

The platform has integrated platform sources by default, so no additional settings are required. Custom sources need to be created according to user needs. Source management refers to the management of custom sources.

Platform Sources

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

Custom Sources

If more tasks or stages need to be used, administrators and project members can write the configuration files of tasks or stages themselves and store the files 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 the source to the project (such sources are marked with Platform), all operations, development, or testing personnel in all namespaces under the project can directly use the source. If the project administrator creates the 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 indicates optional operations.

• If the source corresponding to the code repository has been assigned to the project, 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 new configuration will be automatically applied to the pipelines that reference custom tasks or stages.

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