Integrations / Jenkins

Jenkins

Jenkins automation server for jobs, builds, queues, nodes, artifacts, and CI/CD execution evidence.

Basic auth

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A Jenkins instance Telara can reach.

A user that can read the jobs you care about. Admin is only required for instance-wide settings.

Vendor setup

Get the credential

Open your user configuration

In Jenkins, click your username (top right) → Configure.

Add an API token

In the API Token section, add a new token named for Telara. Copy it immediately; Jenkins will not show it again.

Paste in Telara

Settings → Integrations → Jenkins. Enter the Jenkins URL, your username, and the token.

In Telara

Connect in Telara

Basic auth

Jenkins username and API token. Store base_url in credentials when using a self-hosted Jenkins URL.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Username
API token

Knowledge

What gets indexed

Resource	Coverage
Job	Partial — not every record the vendor holds is synced
Pipeline run	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Job	Up to 1 day	Removed records disappear on the next full sync
Pipeline run	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Job, Pipeline run.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

The token inherits that user’s view of jobs. A narrowly permissioned user is safer and often enough.

Jenkins must be reachable from Telara. A URL that only resolves on your VPN will not connect.