--- title: Jenkins API Integration on Truto slug: jenkins category: CI/CD canonical: "https://truto.one/integrations/detail/jenkins/" --- # Jenkins API Integration on Truto **Category:** CI/CD **Status:** Generally available ## Unified APIs ### Unified CI/CD API - **Artifacts** — The artifact represent an artifact in the CI/CD. - **Builds** — The build represent a build in the CI/CD. - **Workflow** — The workflow represent a CI/CD workflow. ### Unified User Directory API - **Role Assignments** — - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ## How it works 1. **Link your customer's Jenkins account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Jenkins.** The Proxy API is a 1-to-1 mapping of the Jenkins API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Power engineering analytics with CI/CD pipeline data** — SaaS platforms focused on engineering productivity can sync Jenkins build and workflow data to calculate DORA metrics like deployment frequency, lead time, and change failure rate — giving engineering leaders visibility into team performance without custom scripts. - **Automate security scanning as a CI/CD gate** — Security and vulnerability scanning platforms can monitor Jenkins builds, fetch generated artifacts for analysis, and enforce policy gates — enabling shift-left security that runs automatically in the customer's existing pipeline infrastructure. - **Trigger rollback pipelines from incident management tools** — Incident response platforms can let responders browse available Jenkins workflows and trigger rollback builds directly from their war room or Slack, reducing MTTR by eliminating context switches to the Jenkins UI during outages. - **Bridge test management with test execution** — QA and test management platforms can trigger Jenkins workflows when test suites are updated, then pull back test artifacts and build results to display pass/fail metrics natively — closing the loop between test definition and execution. - **Sync Jenkins users and roles for access auditing** — Compliance and identity governance platforms can pull Jenkins user directories, roles, and role assignments to audit who has access to CI/CD infrastructure and ensure RBAC policies are consistently enforced across tools. ## What you can build - **CI/CD deployment velocity dashboard** — Fetch historical builds and workflows from Jenkins to render real-time charts showing deployment frequency, build duration trends, and failure rates across teams and projects. - **One-click rollback trigger from incident timeline** — Let incident responders browse Jenkins workflows and kick off parameterized rollback builds directly from your product's incident dashboard without touching Jenkins. - **Artifact-based security scan orchestration** — Automatically retrieve build artifacts from completed Jenkins runs, feed them into your scanning pipeline, and surface vulnerability results alongside the originating build. - **Jenkins RBAC sync for access reviews** — Pull Jenkins users, roles, and role assignments into your identity governance product so customers can audit CI/CD permissions alongside their other tooling. - **Build status feed in an internal developer portal** — Surface real-time Jenkins build statuses, logs, and triggering user information inside your developer portal so engineers never need to open the Jenkins UI. - **Parameterized pipeline launcher** — Expose a form-driven UI that lists available Jenkins workflows and their required parameters, letting non-DevOps users trigger builds safely from your product. ## FAQs ### How does authentication work for Jenkins integrations through Truto? Jenkins typically supports API token-based authentication (username + API token) and, in enterprise setups, SSO via LDAP or SAML. Truto handles credential storage and auth management so your end users can connect their Jenkins instances securely without you building auth flows from scratch. ### Jenkins is self-hosted — how does Truto connect to on-premise instances? For Jenkins instances behind a firewall or in air-gapped environments, Truto supports proxy-based connectivity so your customers' Jenkins servers don't need to be exposed to the public internet. ### What Unified APIs does Truto offer for Jenkins? Jenkins maps to two Truto Unified APIs: the Unified CI/CD API (covering Artifacts, Builds, and Workflows) and the Unified User Directory API (covering Users, Roles, Role Assignments, and Workspaces). Specific tools are built on request — contact Truto to scope your exact requirements. ### Does Jenkins have API rate limits I need to worry about? Since Jenkins is self-hosted, there are no vendor-imposed rate limits. However, aggressive polling can strain the Jenkins controller. Truto manages pagination and request patterns to avoid overloading your customers' instances. ### Can I trigger parameterized Jenkins builds through Truto? Yes — the Unified CI/CD API's Builds resource supports triggering Jenkins jobs with parameters. This lets you pass dynamic values like git hashes, environment names, or feature flags when kicking off a build. ### Are there pre-built tools available for Jenkins today? Jenkins tools are built on request. Truto scopes the integration to your specific use case and builds the necessary connectors against the Unified CI/CD and User Directory API models, so you get exactly the data and actions you need.