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

Описание и применение

Создан коннектор Jenkins для cognee, позволяющий синхронизировать сборки, маскировать чувствительные данные и искать ошибки по естественному языку.

Задача

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.

Результат

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.

Рабочий процесс

• 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.

Доказательства

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

Источник

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.

Источник

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

Источник

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

Источник