Hacktoberfest: Contribution Chronicles

I'm a developer from Vietnam, and this is my contribution to WeMakeDevs Mergetober: a new data-source connector for cognee.

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

I wanted to ask my CI a plain question — "which build failed last night, and why?" — and get an

answer with the exact error line.

What I built

A Jenkins data-source connector for cognee , an open-source

AI memory engine. It syncs Jenkins jobs and builds into cognee so you can search them in plain language.

PR: https://github.com/topoteretes/cognee-community/pull/296

Issue: https://github.com/topoteretes/cognee/issues/4714

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.

How it works

Small API calls.…