Pipelines Integrations

An Integration connects Pipelines to an external service/tool. Each integration type defines the endpoint, credentials and any other configuration detail required for Pipelines to exchange information with the service. All credential information is encrypted and held in secure storage, in conformance with best security practices.

Using Integrations

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.

Integrations are added through the JFrog Platform. For more information, see Managing Pipelines Integrations.

Environmental Variables

A step that uses an integration can access the integration and its properties through environment variables. The form of the environment variable is:

int_<integration name>_<tag>

For example, if an Artifactory Integration or JFrog Platform Access Token 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 "Published Go binary to $int_myArtifactory_url"

For more information about using environment variables, see Pipelines Environment Variables.

Integration Types

The available integrations for JFrog Pipelines are: