Want to adopt lockable-resources plugin

[Jim Klimov]

Hi everyone,

I would like to adopt the "Lockable Resources" plugin marked as "for adoption" for some time now: https://github.com/jenkinsci/lockable-resources-plugin/ 

• The current status of the plugin is "for adoption". 
• My GitHub username is "jimklimov". 
• My Jenkins infrastructure account ID is " jimklimov ".
• My Artifactory https://repo.jenkins-ci.org/ui/ account ID is " jimklimov " and has logged in before (and today, to be sure).
• The link to the "Repository Permission Updater" PR: https://github.com/jenkins-infra/repository-permissions-updater/pull/2348

Please let me know if there are any additional steps I will need to take in order to complete the adoption process. 

Best regards,

Jim Klimov

-----

As the "Lockable Resources" plugin has been marked for adopt-this-plugin and releases for the past couple of years concerned mostly dependabot updates (but not only - thanks Basil et al for the architectural modernization!), I would like to take up the duties and adopt the plugin in order to keep it maintained in terms of community-contributed features and so to keep it updated, useful, and relevant. Note that I am not a decent Java developer, so would welcome continued PR submissions proposing actual improvements from the community members.

For some past years I had to roll my own fork with my and others' PRs applied over master, in order to have the features my farms rely on. This is not as convenient as just installing a current plugin release from Artifactory and having the features there :)

The link to the concerned GitHub repository is jenkinsci/lockable-resources-plugin

CC @basil who suggested that I (@jimklimov) and/or @offa take over :) in jenkinsci/lockable-resources-plugin#273

Also CC @abayer and @jglick as they had a good architectural view for the plugin discussed in e.g. jenkinsci/lockable-resources-plugin#64 so hopefully might lead me away from mistakes in the future ;) (That said, we do need and use a sort of feature proposed in that PR, implemented elsewhere in a shared library, and I'd love to have an in-core ability to separate the lock() and unlock() activities...)

[Alex]

Heyo,

glad to see that someone picked the plugin up! Make sure to remove the "adopt-this-plugin" topic on GitHub to get a rid of the plugin adoption banner from the plugin manager.

Thanks,

Alex

[Jean-Marc Meessen]

Thank you for stepping in, Jim. This is a plugin I worked with in a previous chapter of my life. I will keep an interested eye on its evolution.

/- Jmm

--
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/538cc5c6-330b-4250-b8d8-15b18eb8583bn%40googlegroups.com.