Hi everyone,
I’m Saviti Veerababu, an undergrad student with a strong background in Java and experience in Python, Django, and C++. I’ve been using IntelliJ IDEA Ultimate since 2022 for my projects, which has made me comfortable with Gradle-based workflows and Java development. I’m excited to apply for GSoC 2025 with Jenkins and am particularly drawn to the “Improving Tekton Client Plugin” project.
I’m motivated to contribute to Jenkins because I love how it empowers CI/CD, and enhancing the Tekton integration feels like a perfect way to blend my Java skills with cloud-native tech. The idea of improving interoperability and user experience for Tekton Pipelines in Jenkins really resonates with me I see it as a chance to make a tool I’d want to use myself.
I’d love to discuss this project with mentors @waveywaves and @krisstern. Specifically, I’m curious about the priority between supporting multiple Tekton versions dynamically versus adding resources like Tekton Chains or Triggers. What do you see as the most impactful starting point for a 175-hour project? I’m also planning a small Java contribution to get familiar any newbie friendly issues you’d recommend?
Looking forward to your thoughts!
Best,
Saviti Veerababu
GitHub: M1D0R1x (M1D0R1x) · GitHub