Docs / Data sources / Jenkins

Jenkins

Business software

Built when you ask for it

Sync Jenkins jobs, builds, and node data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Jenkins connector syncs your build automation data into analytics-ready tables in your data warehouse. Pull jobs, builds, and nodes from the Jenkins Remote Access API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Jobs
  • Builds
  • Nodes

How it gets built

  1. Choose Jenkins when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Jenkins's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Jenkins itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API token (Basic auth). Generate an API token from your Jenkins user security settings and use it as the password in HTTP Basic auth.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Jenkins connector?
Not as a finished connector yet. Ingest builds it from Jenkins's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Jenkins data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Jenkins API documentation: https://www.jenkins.io/doc/book/using/remote-access-api/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Jenkins