JFrog integration with DevOps Change Velocity

Connect to your JFrog instance to track artifacts published to JFrog from pipeline executions in Jenkins, GitHub Actions, Azure DevOps, and GitLab.

For Jenkins, you must activate the Jenkins Artifactory plugin in your Jenkins server to generate the artifacts as part of your pipeline run and publish them in the JFrog artifact repositories.

Note: Historical import of JFrog artifacts is not supported. You can import JFrog artifacts that are built by Jenkins using the Service Catalog import historical data process. For more information, see Importing historical data for DevOps tools. Discover and configure is also not supported for JFrog.

Get started

Use one of the following options to onboard JFrog. For a guided experience, use the workspace to onboard a tool. Alternatively, you can use the Service Catalog or Classic experience.

• Onboard JFrog to DevOps Change Velocity — Workspace
  Connect to your JFrog instance using the DevOps Change Workspace playbook to track artifact repositories published to JFrog.
• Onboard JFrog to DevOps Change Velocity — Service Catalog
  Connect your JFrog instance using the ServiceNow Service Catalog.
• Onboard JFrog to DevOps Change Velocity — Classic
  Connect to an instance of the JFrog artifact tool to enable you to track artifacts published to JFrog.
• Integration with JFrog AppTrust application
  Integrate DevOps Change Velocity with JFrog AppTrust applications to automate change request creation, approval, and evidence collection as application versions are promoted through life-cycle stages.

Parent Topic:Integrating DevOps Change Velocity with third party tools