Pipelines users can view the catalog of successfully loaded extensions, and manage lifecycle staging of each extension version.
From the Application tab go to Pipelines | Extensions, and select the Extensions tab. The the list of extensions most recently synced from extension sources are shown under Latest.
|The named |
|The namespace of the extension.|
|The class of the extension (e.g., resource or step)|
|The source repository path of the extension.|
An extension that has been properly Git tagged with semantic version information can be formally released. When an extension is released, it can be referenced by its version number in a Pipelines DSL. That version of the extension will continue to be available even after a new latest version has been synced from the extension source..
To release the latest version:
If your extension source includes a readme file, you can view the contents of this file. To do this, in Latest, hover over the rightmost region of the row where the extension definition file is listed to reveal the Documentation icon, and then click.
Retiring an extension version will make it unavailable for further use in a Pipelines DSL. You can select an advance date for a version's retirement.
The row of the extension version will be updated to show the retirement date.
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.
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.|
When any of the pipeline config files have changed, you may need to manually sync the pipeline source to reload:
If the Status indicates that the sync failed, click Logs to view the logs of all synchronized files.
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:
To add an Extension Source:
Pipelines will sync the extension source to load the extensions.