Asking my CI "why did it fail?" — a Jenkins connector for cognee
说明与用途
为 cognee 构建了 Jenkins 连接器,实现作业同步、敏感数据掩码,并支持自然语言查询失败信息。
问题
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.
- 记录日期: 2026-10-08T09:55:50.925Z