Add CLI option to opt out of metadata feature (useful for testing and development purposes) #1093.
Dry run - collect metadata locally, don’t push it to the repo
Normal run - collect and push to the repo
skip-metadata - disable both
Clean up of the metadata workflow
Use the commit SHA in action rather than a version tag for security best practices to prevent supply chain attacks.
Shift the workflow implementation to the CLI tool, making it a reusable workflow that is being called in the metadata repository. #1097
For the update metadata workflow, the actions[bot] makes a PR daily via a cron job, and for the merge, we are leaving it to the maintainer for now.
We can track the migration status, i.e., whether the recipe fails or succeeds #1092.
For the next week, I will be focusing on consolidating the metadata to make reports, which will be further consumed by the Jenkins report or the statistics site.
Successfully published the developer mailing list email and a Discourse post regarding the current status of Gatsby and the reasoning behind the move to Vite.
Adopted a layered branching approach for each PR to build on the previous working setup, while keeping merge conflicts isolated.
Improving Tekton Client Plugin for Jenkins - Maeve
Update the Plugin documentation’s README on the existing feature: #416
Successfully implemented and locally tested a E2E pipeline using a kind cluster, based on JenkinsRule, applying JUnit 5 (from Bruno’s update). Will open soon a PR on E2E test include all Tekton feature (Task, TaskRun, Pipeline, PipelineRun)
Vibhav and I had an in-depth discussion and hands-on testing session focused on my understanding of Jenkins plugin development. We thoroughly reviewed the codebase together and identified potential improvements. We might want to migrate the plugin UI from Jelly to React, and this can lead to a good blogpost about migrating from Jelly to React
Projects are on schedule according to mentors. Going through discoveries, testings, trials and error.