Skip to main content

​
Overview

The Jenkins integration connects a Jenkins instance to G360 and lets you select which repositories and pipelines to include for data collection and analysis. Setup has two parts:
  • Connection: the Jenkins server details and credentials.
  • Data scope: the repositories to sync from that connection.

​
Prerequisites

Before you start, make sure you have:
  • Access to the Engineering Metrics area in G360
  • A Jenkins instance that G360 can reach, directly or through a proxy
  • A Jenkins user for the connection, ideally a dedicated read-only service user
  • A Jenkins API token for that user (see Create a Jenkins API token)
  • Overall/Read, Job/Read, and Job/Discover permissions for that user (see Required Jenkins permissions)

​
Create a Jenkins API token

Generate the API token as the connection user.
1

Sign in as the connection user

Log in to Jenkins as the user that G360 will connect with.
2

Open the API token settings

Go to People → the user → Configure → API Token.
3

Generate and copy the token

Click Add new Token and copy the value immediately. You paste it into the connection’s Password field.
Jenkins shows the API token only once. Copy it before you leave the page.
Use a dedicated read-only service user rather than a personal admin account.

​
Required Jenkins permissions

The connection user needs these permissions on every folder in scope: Read-only access is enough. G360 only calls the JSON API for jobs, builds, and changesets, and never triggers or modifies a build.
If a folder has Job/Read but not Job/Discover, Jenkins doesn’t refuse the request. It hides that folder’s children, so the job tree comes back shorter than expected with no error.

​
Create a Jenkins connection

1

Open Jenkins Connections

In Engineering Metrics, select Integration from the left sidebar, then go to Jenkins Connections.
2

Start a new connection

Click New Connection to create one, or select an existing connection to manage it. The Manage Connections: Jenkins window opens.
3

Enter connection details

4

Test the connection

Click Test Connection to validate that the server is reachable and the credentials work. If it fails, see Troubleshooting.
5

Save the connection

Click Save Connection.
Invalid credentials cause the connection test to fail.
The Manage Connections: Jenkins window includes a View Jenkins setup documentation link for help creating a connection. When you edit an existing connection, it also shows a Delete Connection button.

​
Configure data scopes

A data scope tells G360 which repositories to sync from a connection.
1

Select the connection

In 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 window opens and shows the connection name.
3

Find and select repositories

Use the Search by repository name… field to find a repository, then select the checkbox next to it. The table lists Repository Name and Organization, and both columns are sortable.
4

Add the scope

Click Add Scopes. The button stays disabled until you select at least one repository. To close the window without adding anything, click Cancel.

​
Manage connections

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

​
Synchronization and metrics

After you set the connection and data scope, G360 brings in pipeline data from the selected repositories for CI/CD analytics. The sync is read-only: it never triggers or modifies a Jenkins build.

​
Troubleshooting

Possible causes
  • Incorrect Endpoint URL
  • Invalid Username or API Token
  • Jenkins server not reachable from G360 (may need a Proxy)
Actions
  • Check that the endpoint matches your Jenkins instance’s API URL, including any context path.
  • Reenter the credentials. Use the show/hide toggle to confirm you typed the API Token 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 or organization in Jenkins
  • The folder has Job/Read but not Job/Discover, so Jenkins hides its children without an error
Actions
  • Search with a partial name.
  • Confirm the Jenkins account used for the connection has access to the repository.
  • Confirm the account has Job/Discover on every folder in scope.

​
Best practices

  • Use a dedicated account. Use a dedicated Jenkins account rather than a personal login, so the connection doesn’t break if an individual’s credentials change. A read-only service user is recommended.
  • Keep the endpoint URL stable. Avoid changing the Jenkins server URL after you set up the connection, to prevent sync interruptions.
  • Grant only the permissions the integration needs: Overall/Read, Job/Read, and Job/Discover.

​
Summary

The Jenkins integration connects a Jenkins instance to G360. By creating a connection with a read-only API token and adding data scopes for the repositories you need, you bring Jenkins pipeline data into CI/CD analytics.