Pipelines Extensions Tutorial

Add and Sync Extensions

To add your Pipelines DSL extension definitions so they can be used in your pipelines, you must作为exten分叉的存储库添加到管道sion source.

Add an Administration Integration

In theAdministrationmodule,add an administration integrationfor the version control system account (e.g.,GitHub,Bitbucket Server, or other) that holds the source repository for your extensions.

To add an administrator integration for Pipelines DSL extensions:

1. From theAdministrationmodule go toPipelines | Integrations.
2. From the Integrationsview, clickAdd an Integration.
3. In the resultingAdd New Integrationdisplay, click theAdminradio button and then complete the entries for your VCS account and clickCreate.
   
   
4. After entering all the relevant details for the integration, clickTest Connectionto validate all the details you have entered, including the URL, user credentials, and the token for sufficient permissions on the repository.

Add an Extension Source

Once the VCS account has been added to the administration integrations, you can add your source code repository as an extension source.

Your source code repository for your extensions must be structured according to the requirements for thestep modelandresource model.

For example, our sample repository folder structure is:

jfrog-pipelines-extensions-sample -- steps ------ tutorials –- HealthCheck
|
– resources -- tutorials -- test

wheretutorialsidentifies the namespace for each set ofstepsand2022世界杯阿根廷预选赛赛程.

To add an Extension Source:

1. From theApplicationmodule go toPipelines | Extensions & Templates.
2. Select theSourcestab, thenclickAdd Source,and then clickExtensions.
3. In the resultingAdd Extension Sourcedisplay, select the VCS account integration added above, enter the repository path and branch, then clickCreate Source.

Pipelines syncs the extension source to load the extensions.

Click theLogscolumn to view the results of the sync.

Confirm Extensions

View theExtensionstab to see the list of successfully loaded Pipelines DSL extensions.

Example Pipeline

The example pipelineMyHealthCheckis in thepipelinebranch of the repository. TheMyHealthCheckpipeline will test the newly added step and resource extensions.

resources: - name: MyGitHub type: GitRepo configuration: path: jfrogtw/jfrog-pipelines-extensions-sample # <-- Change to your repository path gitProvider: tw_github # <-- Change to your GitHub integration - name: MyTest type: tutorials/test configuration: alpha: "JFrog" number: 42 flag: true pipelines: - name: MyHealthCheck configuration: environmentVariables: readOnly: my_env_var: "hello" steps: - name: Health_Check_Step type: tutorials/HealthCheck configuration: healthCheckUrl: "//www.si-fil.com" notifyOnSuccess: false notifyOnFailure: false stuff: - "This is a string" - "This is another string" inputResources: - name: MyTest - name: MyGitHub

Add the Pipeline Source

To load the example pipeline in your Pipelines deployment, add thepipelinebranch of the repository as a Single Branch Pipeline Source.

If you have not already, you will need to add an integration for your GitHub account. Note that this is in addition to the administration integration added above (even though it is for the same account).

When you clickCreate Source, the Pipelines DSL file will be synced from the newly added pipeline source. When completed, you can view theLogsfor the sync.

Run the Example Pipeline

The newly loaded pipelineMyHealthCheckcan be seen in theMy Pipelinesview.

Click onMyHealthCheckto view itsPipeline History. You can click on the pipeline's singleHealth_Check_Stepto trigger a run of the pipeline.