Hi Oleg, Thank you for your response and your insights, I've taken note of those key items. About the onboarding, sounds great creating a thread, I'm new to the Jenkins development community, so I would trust whichever option you give me (this thread or on community.jenkins.io). A dedicated Jenkins developer meeting sounds pretty good, I should warn you again that I'm new to Jenkins plugin development, I have years of experience using Jenkins, but not much on Jenkins development but I'm eager to learn and contribute. I'll be reading a lot more about Jenkins development, and I found some tutorials about plugin development that I'm going to be working on, to have more context before that Jenkins Developer meeting.
On Sunday, July 11, 2021 at 12:57:29 AM UTC-6 Oleg Nenashev wrote: > Hi Roberto, > > Thanks again for stepping up as a maintainer. It is much appreciated. This > plugin is essential for many large scale instances, and it has its uses > even in the container CI/CD environments. Unfortunately I did not have > enough time to properly maintain and evolve this plugin :( > > I am currently taking a break from the Jenkins community due to personal > community unrelated reasons, but I plan to be back in August or so. If you > have some time and interest, I would be happy to share my vision for this > plugin and to help with onboarding. I could do it in this thread, or we > could start a community.jenkins.io discussion. Later we could also have a > dedicated Jenkins developer meeting. What do you think? > > Just key items from my mental backlog: > > - Removing dependency on Extended Choice plugin, restoring the tool > versioning engine > - Better Pipeline compatibility ( > https://issues.jenkins.io/browse/JENKINS-30680) > - Better JCasC integrations, including support for templating and > advanced configuration export > - Introducing a "Container Image Selector" capability for tools > packaged as Docker images. It would allow using the plugin in Docker and > K8s environments more easily, and the engine would be more or less similar > - Introducing traceability of tool usages using Jenkins fingerprints > engine and UI > - Unraveling the tool/environment management logic and making it more > simple. Or at least documenting the behavior > - Moving issues to GitHub issues and doing issue scrub in Jira > > Best regards, > Oleg Nenashev > > > On Sunday, July 11, 2021 at 3:34:36 AM UTC+2 [email protected] wrote: > >> Thank you Ulrich, >> >> I've already filed a pull request: >> https://github.com/jenkins-infra/repository-permissions-updater/pull/2018. >> The two validations for de PR passed, but the PR hasn't been merged, so I >> was wondering who should do with that? >> >> Also I was wondering how or who would give me access to the github repo >> for the plug-in? >> >> Thanks for al the help! >> >> >> >> On Thursday, July 8, 2021 at 12:27:38 PM UTC-6 [email protected] >> wrote: >> >>> Hi Roberto, >>> >>> Thanks for helping to keep the custom-tools-plugin alive! >>> >>> Since this plugin is already up for adoption we can directly proceed >>> with the next steps: >>> Please read >>> https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ and >>> then file a pull request >>> for https://github.com/jenkins-infra/repository-permissions-updater. >>> >>> Ulli >>> >>> Am 07.07.2021 um 06:30 schrieb Roberto Hernandez <[email protected]>: >>> >>> >>> Hi, >>> >>> I would like to become a maintainer of the following plugin: >>> >>> URL: https://plugins.jenkins.io/custom-tools-plugin/ >>> Github username: https://github.com/robertohern83 >>> Jenkins infrastructure account id: rhernandezm >>> >>> I have some ideas to improve it, but I don’t have yet a PR, I wanted to >>> understand a little bit more about the process to send changes first. >>> >>> >>> _____ >>> Mag. Roberto Hernández Montoya >>> >>> >>> <image001.png> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CH0PR03MB6116D2E66EAD06EA6DAC3DB6A21A9%40CH0PR03MB6116.namprd03.prod.outlook.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CH0PR03MB6116D2E66EAD06EA6DAC3DB6A21A9%40CH0PR03MB6116.namprd03.prod.outlook.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/17a814d7-d9e5-41b4-a689-efb315c9ae79n%40googlegroups.com.
