Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About Jenkins

Iru calls the Jenkins remote API with HTTP Basic authentication: username plus an API token as the password (preferred over a real password). The wizard first stores jenkins_host (hostname and optional context path only), then collects credentials.

​
How it works

Authorization: Basic base64(username:api_token)
DetailValue
CategoryCI/CD
AuthenticationBasic (user + API token)
Official references: Scripted clients, API tokens, Remote API.

​
Prerequisites

  • Jenkins reachable from Iru’s network (firewall / VPN / allowlist as needed).
  • A user with Overall/Read and job-level read access for the scope you audit.
  • HTTPS strongly recommended for the controller.

​
Connect Jenkins to Iru

​
Jenkins

1

Open your user API token settings

Sign in to Jenkins. Click your username, then Configure. Open the API Token section (or equivalent for your Jenkins version).
2

Create and copy an API token

Choose Add new Token, name it (for example Iru Compliance), then Generate. Copy the token once when Jenkins shows it.Optional expiry may apply; Jenkins also surfaces aging tokens in the UI so you can rotate before they lapse.

​
Iru Compliance

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on Jenkins

Find Jenkins (set Category to Developer tools or use Search by name or description). On that card, turn on the toggle. A browser tab or window may open for the connector wizard.
3

Enter Jenkins host

Enter jenkins_host as jenkins.example.com or jenkins.example.com/jenkins (without https://). Confirm server variables.
4

Enter credentials and activate

Enter username and paste the API token into the password field. Submit until the Jenkins card shows Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Toggle source off/on for a fresh wizard session.
Correct user/token; user needs read permissions on target jobs.
Routing, TLS, VPN, or allowlist for Iru egress.
Include context path if Jenkins is not at domain root.

​
Considerations

Use a read-only service user scoped to the folders…

Use a read-only service user scoped to the folders or views you need.

​
See also