Hi Jenkins Community,
I’m Maeve Ho, a GSoC 2025 contributor working on enhancing the Jenkins Tekton Client Plugin under the guidance of my mentors @poddingue, @krisstern and @waveywaves. I’m excited to collaborate with you all to improve how Jenkins and Tekton work together in cloud-native CI/CD pipelines.
What is the Tekton Client Plugin?
The Tekton Client Plugin enables Jenkins to interact with Tekton, a Kubernetes-native CI/CD framework. It allows Jenkins users to create and delete Tekton resources like Tasks, Pipelines, and PipelineRuns directly from Jenkins pipelines.
Why is it important for the community?
As more organizations adopt Kubernetes-native tooling, Tekton becomes an essential building block for scalable, declarative CI/CD. This plugin helps:
- Bridge Jenkins and Kubernetes: Leverage Jenkins’ mature ecosystem with Tekton’s cloud-native execution engine.
- Simplify operations: No need to manually switch between Jenkins and
kubectlto manage pipelines. - Unify workflows: Run traditional Jenkins jobs alongside modern Tekton Pipelines in one place.
What to expect this summer?
Through my GSoC project, I aim to:
- Implement full CRUD support for all major Tekton resource types
- Add support for reading logs, modifying resources, and enhanced error handling
- Develop user-friendly Jenkins pipeline steps for Tekton interactions
Why use the Tekton Client Plugin?
This plugin is ideal for teams modernizing their CI/CD workflows. It helps you:
- Run Kubernetes-native pipelines from Jenkins
- Reduce manual overhead and context switching
- Move toward hybrid cloud automation, combining legacy Jenkins jobs with cloud-native tasks
If you use the plugin or have ideas for how it could serve you better, I’d love to hear your thoughts! Your input will help shape the direction of this plugin to better meet the needs of Jenkins and Kubernetes users alike.
Thanks, and looking forward to an exciting summer!
Best,
Maeve
