GSoC Office Hour June 25, 2025

Contributing GSoC
1

Will begin in 1 hour.

Agenda and call in info are at Jenkins GSoC 2025 Office Hours Meeting Agenda and Notes - Google Docs.

Meeting notes and recording will be shared below after the meeting.

thanks,
alyssa

1 Like
2

Attendees: Alyssa, Kris, Giovanni, Raunak, Phillipp, Valentin, V, Chirag, Birajit Saikia, Maeve Ho

Agenda:

Status Updates

  • Improving Tekton Client Plugin for Jenkins - Maeve Ho

    • Set up and run Tekton pipeline and Jenkins with Tekton plugin on the same Kind cluster for integration tests (Task, TaskRun, Pipeline, PipelineRun) Jenkins + Tekton Integration on Kind Cluster - HackMD
    • However, did not really run it with the plugin but used mainly k8s resources and tekton pipeline. Working on running using the plugin
    • Documented existing feature for better understanding: Jenkins Tekton Plugin - Feature Documentation - HackMD
    • Set up extra weekly meeting for catching up
    • WIP: Creating a PR to update the README for what already exists in the repo, implement integration tests and e2e test for the plugin itself

  • Improving Plugin Modernizer - Raunak Madan

    • Fix precondition bug #1073
    • Validate modernization metadata before pushing from the CLI tool #1074
    • Added Workflow for Validation and Auto-merge. Currently we have a minimal implementation of validation, will improve more in the future.
    • Now able to track the latest commit SHA for the default branch.
    • Will focus on adding a CLI option to opt out of the metadata feature, cleanup on workflows, and some minor fixes.

  • Complete Build Retooling of Jenkins.io - Birajit Saikia

    • Significant technical decision made to migrate from Gatsby to Vite.js for non-versioned content.
      • The shift is driven by the declining maintenance and ecosystem activity around Gatsby. Recommendation came from Kris, relayed via Zbynek, and was discussed within the team.
    • Migration is actively in progress
      • New Vite-based PRs replicating the previously submitted Gatsby pages are underway
      • Some hiccups in the pages being blank and not showing content so working on that now to fix
    • Composed a draft email to inform the Jenkins developer community about the Gatsby deprecation and the rationale behind the stack migration. It’s in review mode before confirmation by mentors .
    • Part 4 and Part 5 Antora PRs have been reviewed and merged:
    • Work on event sub-pages and pipeline step reference pages is currently paused until the Vite.js migration stabilizes.
    • I have also raised all issues for us to track the Vite.js work in our new vite repo: docs.jenkins.io-vite.js-site repo
      • I will sent invites as collabs to mentors in that repo after I raise my first PR in that
    • Also, I have been preparing PR for the new changes again in Antora, so to finalise the previous LTS baseline changes totally to a new branch and begin other works in Antora aligns with the new Jenkins LTS baseline.
    • Daily progress updates-

  • Jenkins Domain Specific LLM - Chirag Gupta

    • Opened a PR for the final prototype.
    • Self-study on MCP and Agents.
    • Research on whether fine tuning will be necessary or not for the project
    • Work on testing!
      • Made 7 test files, 3 more will be made. Which will be given to mentors to evaluate the responses.
      • Searching for the evaluation metrics for the dataset to be made. And making some examples for mentors to see which will be the focus for this week.
    • The project is moving towards an Agentic approach.
    • Exploring frontend options.

  • AI-Powered Chatbot for Quick Access to Jenkins Resources - Giovanni Vaccarino

    • Last week I concluded my main exam period :slight_smile:
    • Work on UI
      • Implemented fixes and suggestions made by mentors on PR #13
      • The PR have been merged
      • V mentioned more work will be required for the styling
      • Some more enhancements will be implemented
    • Work on Testing
      • Started working at unit tests for the backend
      • Opened a draft PR: #14
      • Asked for some early feedback to the mentors to ensure I’m going in the right direction
    • For the following week the main work will be on the testing part

  • Midterm evaluation (for GSoc contributors):

    • Per Google: “Reminder emails sent 10 days before Evaluation period opens and again within a few minutes of the Evaluation Period opening. If you got an extension for your project then the dates might be different but you can review it in your dashboard.” Best bet is to refer to your individual Google portal for deadlines.