This documentation is for the Technical Preview of JFrog Pipelines, available exclusively to JFrog Enterprise+ customers

Skip to end of metadata
Go to start of metadata

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.

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 without a resource. 

Integrations are added through the JFrog Pipelines UI. For details, see Adding Integrations.

Environment Variables

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

int_<integration name>_<tag>

For example, if an Artifactory Integration is named myArtifactory, then: the environment variable int_myArtifactory_url might be used to send a notification:

  . . .

  - name: publish_go_binary
  type: GoPublishBinary
    - name: build_go
    targetRepository: my-go
    - name: myArtifactory
       - send_notification notifySlack --text "Publshed go binary to $int_myArtifactory_url"

  • No labels