- This line was added.
- This line was removed.
- Formatting was changed.
An Integration connects JFrog Pipelines to an external service/tool. Each integration type defines the endpoint, credentials and any other configuration detail required for Steps in a Pipeline to interact with the source. All credential information is encrypted and maintained separately from the pipeline definition, and held in a secure storage in conformance with best practices.
Integrations are most commonly used in Resources to connect inputs and outputs to the external facility. They can also be referenced directly in many Utility Functions. Integrations can also be directly used as an input to a Step without a resource.
Integrations are added through the JFrog Pipelines UIPlatform. For details, see Adding Managing Pipelines Integrations.
A step that uses an integration can access the integration and its attributes through environment variables. The form of the environment variable is:
For example, if an Artifactory Integration is named
myArtifactory, then: the environment variable
int_myArtifactory_url might be used to send a notification:
steps: . . . - name: publish_go_binary type: GoPublishBinary configuration: inputSteps: - name: build_go targetRepository: my-go integrations: - name: myArtifactory execution: onSuccess: - send_notification notifySlack --text "Publshed go binary to $int_myArtifactory_url"
The available integrations for JFrog Pipelines are: