Skip to main content

​
Overview

The Jenkins integration lets you connect a Jenkins instance to G360 and select which repositories/pipelines should be included for data collection and analysis. Setting up the integration involves two steps:
  1. Create a Jenkins connection (server details and credentials).
  2. Add a data scope to that connection (select which repositories to sync).
1

Open Engineering Metrics

Open the Engineering Metrics platform.
2

Go to Integration

Select Integration from the left sidebar.
3

Open Jenkins Connections

Go to Jenkins Connections.
4

Start a new connection

Click New Connection to create one, or select an existing connection to manage it.
The Manage Connections: Jenkins modal includes a link to check out the documentation if you run into problems creating a connection.

​
Creating a connection

Clicking New Connection opens the Manage Connections: Jenkins modal. Fill in the following fields:
Invalid credentials will cause the connection test to fail.
Once the fields are filled in:
  1. Click Test Connection to validate the server is reachable and the credentials work.
  2. Click Save Connection.
The modal also includes a View Jenkins setup documentation link, and — when editing an existing connection — a Delete Connection button.

​
Adding a data scope

After a connection is created, add a data scope to tell Engineering Metrics which repositories to sync.
1

Select the connection

From the Connections list, select the Jenkins connection you want to configure.
2

Open Add Data Scope

Click the data scope action for that connection. The Add Data Scope modal opens, showing the connection name.
3

Find the repository

Use the Search by repository name… field to find the repository you want to add.
4

Select it

Check the box next to the repository. The table lists Repository Name and Organization, and both columns are sortable.
5

Add the scope

Click Add Scopes. This button stays disabled until at least one repository is selected. Click Cancel to close the modal without adding anything.

​
Managing connections

The Connections list shows, for each Jenkins connection:
  • Connection name and when it was last updated (e.g. “2d ago”)
  • Scope Config — shows Default for the configured scope
  • Actions — icons to edit the scope config or delete the connection
Deleting a connection removes it, along with any data scopes configured under it.

​
Troubleshooting

Possible causes
  • Incorrect Endpoint URL
  • Invalid Username or Password
  • Jenkins server not reachable from Engineering Metrics (may need a Proxy)
Resolution
  • Double-check the endpoint matches your Jenkins instance’s API URL
  • Re-enter credentials, using the show/hide toggle to confirm the password was typed correctly
  • If Jenkins sits behind a firewall, add a Proxy address
Possible causes
  • The repository name doesn’t match your search term exactly
  • The connection doesn’t have access to that repository/organization in Jenkins
Resolution
  • Try searching with a partial name
  • Confirm the Jenkins account used for the connection has access to the repository

​
Best practices

Use a dedicated integration account rather than a personal login, so the connection doesn’t break if an individual’s credentials change.
Avoid changing the Jenkins server URL after the connection is set up, to prevent sync interruptions.