From fc5b2d723987a426592c10149faaf81349d5d87b Mon Sep 17 00:00:00 2001 From: Martin Pokorny <89339813+mPokornyETM@users.noreply.github.com> Date: Fri, 13 Jan 2023 16:32:08 +0100 Subject: [PATCH] It is no more possible to read resource-labels generated in the release 1102.vde5663d777cf (#440) * is no more possible to read resource-labels from config file org.jenkins.plugins.lockableresources.LockableResourcesManager.xml generated in the release 1102.vde5663d777cf * Typo * Update README.md * Update README.md --- README.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/README.md b/README.md index 734946b2c..1dc08c10f 100644 --- a/README.md +++ b/README.md @@ -173,6 +173,29 @@ Reassign | STEAL | Reserves a resource that may be or not be reserved by some pe Reset | UNLOCK | Reset a resource that may be reserved, locked or queued. Note | RESERVE | Add or edit resource note. +## Upgrading from 1102.vde5663d777cf + +Due an [issue](https://github.com/jenkinsci/lockable-resources-plugin/issues/434) **is not possible anymore to read resource-labels** from the config file org.jenkins.plugins.lockableresources.LockableResourcesManager.xml, **which is generated in the release** [1102.vde5663d777cf](https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/1102.vde5663d777cf) + +This issue does not **effect** instances configured by [Configuration-as-Code](https://github.com/jenkinsci/configuration-as-code-plugin) plugin. + +A possible solution is, to remove the `` tags from your `org.jenkins.plugins.lockableresources.LockableResourcesManager.xml`config file manually, before you upgrade to new version (Keep in mind, that a backup is still good idea). + + +Example: + +change this one +``` + + tests-integration-installation + +``` +to +``` + + tests-integration-installation + +``` ## Changelog