Hello Everyone, I’m Swarnendu Majumder, a CS student interested in developer tooling and CI/CD systems. I’m drafting a concise proposal focused on improving developer experience in Jenkins using AI-assisted tooling.
I have experience building backend and automation systems, and I’m interested in applying AI in a practical, maintainable way that aligns with Jenkins’ plugin-driven architecture.
I had a few questions after looking into common Jenkins pain points:
-
Support load: Many issues repeat around pipeline failures and plugin configuration. Would maintainers be open to AI-based, in-product guidance grounded in official docs and issue history to reduce this load?
-
Configuration safety: Would AI-assisted, read-only validation or explanation of pipeline configurations be useful before execution?
-
Ecosystem scale: Given the rapid evolution of plugins, would per-plugin, version-aware guidance be preferable to a global knowledge base?
I’m currently exploring Jenkins core and Pipeline internals. Are there specific subsystems where contributors can have the most impact?
Looking forward to your feedback.