Pipeline Step Documentation Generator improvementsand also find the
Plugin Health Scoring systemidea interesting. Thank you.
I recommend that you start with https://www.jenkins.io/doc/developer/
More specific to Jelly, you have https://www.jenkins.io/doc/developer/forms/jelly-form-controls/
The how-to's might also help you to get started.
Thank you for your interest. You're very welcome to join and contribute to our Ecosystem. The plugin health score is taking more and more substance and will make it in the final list.
Don't hesitate to join us during the GSoC "Office Hour" where we will discuss and clarify projects. This week we will have the EMEA (Europe/Middle-East/Africa) edition (14:00/2PM UTC). Next week will be the Pacific edition (03:00/3AM UTC). We will be alternating meetings to try to cover the globe conveniently.
git maintenancefrom https://git-scm.com/docs/git-maintenance for ideas of the types of problems that can exist for git repositories and that benefit from maintenance tasks. Consider alternatives available to perform similar maintenance tasks on a Jenkins controller or on Jenkins agents. Explore the scheduling alternatives available with Jenkins. Install a Jenkins controller, create a multibranch Pipeline with a GitHub branch source provider and look at the caches created on the Jenkins controller. Consider how the Jenkins controller created those caches and how a maintenance job would find those caches and schedule the maintenance work on those caches. Compare the maintenance task results with command line git and JGit. Are all the maintenance operations feasible in JGit.
@DevUt: in an async environment, its usually good practice to not ask yes/no questions, but instead ask questions with details/context.
"Do we have a mentor for the plugin health project yet?"
12 hours later
12 hours later
"okay i'm interested"
"I'm interested in helping out as a mentor for the plugin health project, is there a mentor yet?"
you saved a bunch of back and forth (just an example, i have no idea why your asking)