Onboard JFrog to DevOps Change Velocity — Workspace
- UpdatedJan 30, 2025
- 4 minutes to read
- Yokohama
- DevOps
Connect to your JFrog instance using the DevOps Change Workspace playbook to track artifact repositories published to JFrog.
Before you begin
Complete the tasks specified in the Getting started with DevOps Change Velocity topic.
Role required: sn_devops.admin or sn_devops.tool_owner
Procedure
-
Navigate to Workspaces > DevOps Change Workspace and use one of the following options to open the Playbook to onboard JFrog.
Option Steps Homepage - Select the Connect tool widget
- On the Connect to a tool modal, select JFrog from the Artifact category.
Applications module - Select Applications (
).
- Select an existing application, or create one. To create an application, see Create an application - Classic.
- From the Recommended actions pane, select the Connect a tool card.
- On the Connect to a tool modal, select JFrog from the Artifact category.
Tools module - Select Tools (
).
- From the Capability list, select Artifact.
- Select Connect a tool.
- On the Connect to a tool modal, select JFrog.
-
Specify a name for the tool in the Tool name field, and select Next.
-
On the JFrog instance details playbook activity:
- Enter the URL of your JFrog instance.
- Enter the login credentials of the global admin for the JFrog instance.
- (Optional)
Select the MID Server option and enter its details if your JFrog instance is attached to a MID Server.
A MID server is required if your tool instance is hosted on-prem. For more information about MID server, see MID Server selection.
- Select Connect.
-
Permission checks are run on the credentials that you entered.
Permissions required and permissions that are available are displayed. If you want to enter credentials with better permissions, select Re-enter credentials. The credentials that you specified must have the Administer Platform role in JFrog for seamless discovery and import of tool objects. This is a limitation from JFrog. For detailed information on all the required permissions, see Jira permissions in Permissions required for DevOps tools.You can choose to continue with the tool connection even if you don't have all the required permissions.Note: If your tool credential has changed, you must update the credentials in your ServiceNow instance. For more information, see Update third-party tool credentials in DevOps Change Velocity.
- Select Next.
-
Specify the access for the tool.
- If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.The tasks these users in the groups can perform depends on the role assigned to them.
- DevOps Tool Owner role: Can view and edit the tool.
- DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
- DevOps Administrator role: Can edit all tools.
- Other DevOps roles: Can view the tool.
Note: If you don't select a group and skip this step, all users with the DevOps Tool Owner role will be able to edit the tool. - If you choose to control access to the tool, the All App Owners can view and associate tool objects to applications option becomes available for selection.
This option enables all users having the DevOps App Owner role to access the tool. If selected, they’ll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.
- Select Assign.
- If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.
-
From the Summary page, select View tool record to review the details of the connected instance.
Result
You’ve successfully onboarded your JFrog tool to DevOps Change Velocity.