Pipelines users can view the catalog of successfully loaded extensions, and manage lifecycle staging of each extension version.
To view the the list of loaded extensions and their versions, from the Application tab go to Pipelines | Extensions, and select the Extensions tab.
|The named |
|The semantic version number of the extension, derived from the directory path of the extension definition in the extension source.|
|The class of the extension (e.g., resource or step)|
|The current stage setting of the extension version.|
|The source repository path of the extension.|
|If shown, the date and time the extension version was (or will be) retired.|
Administering Extension Lifecycles
To change the lifestyle stage of an extension version, click the row to view the extension version's settings, then click Edit.
The Lifecycle Stage field can be changed by selecting a setting in the dropdown list. Changes are restricted according to the current lifecycle stage setting.
|Can be changed to:|
An extension version can be retired from use from an assigned date. When an extension version is retired, it can no longer be used in a pipeline, and an attempt to run a pipeline that uses it will fail.
Managing Extension Sources
An Extension Source represents a source control repository (such as GitHub or BitBucket) where Pipelines extension definition files can be found. An extension source connects to the repository through an administration integration.
Once an extension source is added, Pipelines will automatically load all extension definition files from that repository and its subdirectories.
Viewing Extension Sources
To view the the list of configured extension sources, from the Application tab go to Pipelines | Extensions, and select the Extension Sources tab.
The tab displays the list of configured extension sources that Pipelines will load extensions from.
Each row of the extension sources list includes the following:
|The source repository path of the extension source|
|The source repository branch|
|The success/failure status of the last sync|
|The time and date of the last sync|
|The username of the VCS user who made the triggering change|
|The commit SHA that triggered the last sync|
|Click the Logs link to view the log from the last sync. Use this to diagnose a failure to sync a pipeline source.|
Sync Extension Source
When any of the pipeline config files have changed, you may need to manually sync the pipeline source to reload:
- Hover over the row in the extension source list at the far right until the Sync icon appears.
- Click the Sync icon.
If the Status indicates that the sync failed, click Logs to view the logs of all synchronized files.
Adding an Extension Source
An extension source can be added only by an administator user or a user with resource manager permissions.
Currently, Pipelines permits only a single extension source.
Prerequisites for extension sources:
- An administration integration must be available for the source control account.
- The source code repository for your extensions must be structured according to the requirements for the step model and resource model.
To add an Extension Source:
- From the Application module go to Pipelines | Extensions.
- Select the Extension Sources tab, then click Add an Extension Source .
- In the resulting Add Extension Source display, select the source control account integration, enter the repository path and branch, then click Create Source.
Pipelines will sync the extension source to load the extensions.