List view
Feature is is accepted as described and can be developed. This list is planned for 2025
Overdue by 3 day(s)•Due by December 31, 2025•76/106 issues closedProvide shared library which extended functionality lockable-resources-plugin as a groovy code. The goal is to extend plugin functionality in simple way and provide a solution for end-user with much more then one lock() step. Many users has own solutions to create resources, or check is isFree() ... and are done by interacting with origin Java code. This might hard to make changes here, because nobody can grant, that it works for end-user instances. In this case we can provide more functionality and customizing as well (edit some groovy lib in forked repo is much more ease then edit Java code and build the plugin self) See also discussion here. https://github.com/jenkinsci/lockable-resources-plugin/discussions/445 https://github.com/jenkinsci/lockable-resources-plugin/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+for+Groovy+shared+library%22
No due date•2/11 issues closedWe have a lot of open issues and PRs that are more or less finish, or can not be done. This project shall clean up all of them. ## Issues + Clarify current state of the issue. Is still open / necessary / maybe duplicate. + Close the issue or extend what is to do. + In case it is duplicated add the label https://github.com/jenkinsci/lockable-resources-plugin/labels/duplicate and close the issue. + Set proper labels, milestone and project, that everybody know, what is to do. ## PRs + Try to ping origin contributor to finish the job. + Clarify if we need it. Is open / necessary / possible to merge / do we have permissions to commit in origin branch? + PRs with addressed merge-conflict shall contains label https://github.com/jenkinsci/lockable-resources-plugin/labels/got%20conflicts. + Set proper labels in the PRs. + In case it is duplicated add the label https://github.com/jenkinsci/lockable-resources-plugin/labels/duplicate and close the PR. ## Documentation + Document it, when needed or assigned to https://github.com/jenkinsci/lockable-resources-plugin/milestone/2 + Set the label https://github.com/jenkinsci/lockable-resources-plugin/labels/documentation ## Others + Do whatever is necessary to clean all the historical relicts. It is really hard to get the overview Acceptant criteria: This list must be empty https://github.com/jenkinsci/lockable-resources-plugin/labels/Triage
No due date•16/51 issues closedThis project shall improve our documentation. In many cases we have new issues, that are done for longer time, but nowhere documented. It will be fine, when: + docs for end-users + docs for Jenkins-admins + docs for developers + limitations + ... We have also many open issues, marked for documentation. As outcome shall be following list empty: https://github.com/jenkinsci/lockable-resources-plugin/labels/documentation Please keep in mind, that we shall discuss first steps with docu-profis like @MarkEWaite to get rid about new struct what shall be documented .... The date is not set, because it will be an ongoing process
No due date•5/9 issues closed