<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Jagavantha PA</title>
    <description>The latest articles on Forem by Jagavantha PA (@jaga0001).</description>
    <link>https://forem.com/jaga0001</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3163553%2Fba93cc42-9fcf-496b-9f16-858009ac1b6b.jpg</url>
      <title>Forem: Jagavantha PA</title>
      <link>https://forem.com/jaga0001</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jaga0001"/>
    <language>en</language>
    <item>
      <title>RepoPilot: Building a Self-Healing CI/CD Agent with Elasticsearch Semantic Memory</title>
      <dc:creator>Jagavantha PA</dc:creator>
      <pubDate>Wed, 11 Mar 2026 05:02:10 +0000</pubDate>
      <link>https://forem.com/jaga0001/repopilot-building-a-self-healing-cicd-agent-with-elasticsearch-semantic-memory-23f0</link>
      <guid>https://forem.com/jaga0001/repopilot-building-a-self-healing-cicd-agent-with-elasticsearch-semantic-memory-23f0</guid>
      <description>&lt;p&gt;👨‍💻 Why I’m Building Systems That Learn&lt;br&gt;
As a B.Tech student in Artificial Intelligence &amp;amp; Data Science, I’ve always been fascinated by one core question:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Why do systems repeat the same mistakes when they already have the data to avoid them?&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;During my journey as a Python developer, I’ve worked with CI/CD pipelines, cloud deployments, and DevOps workflows. One pattern kept bothering me — build failures were rarely new problems. They were recurring problems.&lt;/p&gt;

&lt;p&gt;The logs were there.&lt;br&gt;
The fixes were in commit history.&lt;br&gt;
The knowledge existed.&lt;/p&gt;

&lt;p&gt;But the system had no memory.&lt;/p&gt;

&lt;p&gt;As someone exploring the intersection of AI agents, backend systems, and DevOps automation, I wanted to build something that doesn’t just automate pipelines — but helps them learn.&lt;/p&gt;

&lt;p&gt;That curiosity led to RepoPilot — a self-healing CI/CD agent powered by semantic search and vector memory.&lt;/p&gt;

&lt;p&gt;This article documents not just a project, but a shift in thinking:&lt;/p&gt;

&lt;p&gt;From reactive debugging&lt;br&gt;
To intelligent, memory-driven DevOps.&lt;/p&gt;

&lt;h2&gt;
  
  
  📍The Problem: CI Has No Memory
&lt;/h2&gt;

&lt;p&gt;In most development teams, CI failures follow a predictable pattern:&lt;/p&gt;

&lt;p&gt;A build fails&lt;br&gt;
A developer investigates&lt;br&gt;
The issue is fixed&lt;br&gt;
The solution disappears into the commit history&lt;br&gt;
Weeks later, a similar failure appears again.&lt;/p&gt;

&lt;p&gt;The logs exist.&lt;br&gt;
The fix exists.&lt;br&gt;
But the connection between them is lost.&lt;/p&gt;

&lt;p&gt;CI systems detect failures efficiently — but they do not understand them.&lt;/p&gt;

&lt;p&gt;That gap is where this project begins.&lt;/p&gt;

&lt;p&gt;📖 Read the full article on Medium:&lt;br&gt;
&lt;a href="https://medium.com/@jagavanthaarunkumar/repopilot-building-a-self-healing-ci-cd-agent-with-elasticsearch-semantic-memory-3aa511b64daf" rel="noopener noreferrer"&gt;https://medium.com/@jagavanthaarunkumar/repopilot-building-a-self-healing-ci-cd-agent-with-elasticsearch-semantic-memory-3aa511b64daf&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>elasticsearch</category>
      <category>hackathon</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
