https://plugins.jenkins.io/custom-tools-plugin/ adoption

49 views
Skip to first unread message

Roberto Hernandez

unread,
Jul 7, 2021, 12:46:55 AM7/7/21
to jenkin...@googlegroups.com

 

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

 

Diagram

Description automatically generated

Ullrich Hafner

unread,
Jul 8, 2021, 2:27:38 PM7/8/21
to JenkinsCI Developers
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:

Ulli

Am 07.07.2021 um 06:30 schrieb Roberto Hernandez <roberto...@gmail.com>:

 
Hi, 
 
I would like to become a maintainer of the following plugin: 
 
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CH0PR03MB6116D2E66EAD06EA6DAC3DB6A21A9%40CH0PR03MB6116.namprd03.prod.outlook.com.

Roberto Hernandez

unread,
Jul 10, 2021, 9:34:36 PM7/10/21
to Jenkins Developers
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!

Oleg Nenashev

unread,
Jul 11, 2021, 2:57:29 AM7/11/21
to Jenkins Developers
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

Roberto Hernandez

unread,
Jul 13, 2021, 11:46:40 PM7/13/21
to Jenkins Developers
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. 
Reply all
Reply to author
Forward
0 new messages