Asking my CI "why did it fail?" — a Jenkins connector for cognee

Description and use

A Jenkins connector for cognee was built to sync jobs and builds, mask secrets, and enable plain‑language queries for failures.

Problem

When a Jenkins build fails, the reason is usually a few lines at the bottom of a long console log. A week later nobody remembers which job broke, or why.

Outcome

The connector successfully syncs Jenkins jobs and builds, masks sensitive log data, and allows querying failures via cognee. Deletions in Jenkins are propagated to cognee.

Workflow

• 1. Run Jenkins locally in Docker with sample jobs.
• 2. Sync Jenkins data into cognee using the new connector.
• 3. Query cognee for the last failed build and receive the job name and exact error line.
• 4. Delete a job in Jenkins and sync again to confirm deletions are reflected in cognee.

Evidence

When a Jenkins build fails, the reason is usually a few lines at the bottom of a long console log.

Source

It stores one record per job and one per build: result, time, duration, what started it, and for failed builds the end of the console log.

Source

The answer named the job and the exact error, and the stored log shows the token masked.

Source

I used Claude Code as a coding assistant to write and test the connector, and I reviewed the code before opening the PR.

Source