Skip to content

Commit

Permalink
It is no more possible to read resource-labels generated in the relea…
Browse files Browse the repository at this point in the history
…se 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
  • Loading branch information
mPokornyETM authored Jan 13, 2023
1 parent 692f5d2 commit fc5b2d7
Showing 1 changed file with 23 additions and 0 deletions.
23 changes: 23 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<string>` 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
```
<labels>
<string>tests-integration-installation</string>
</labels>
```
to
```
<labels>
tests-integration-installation
</labels>
```
## Changelog
Expand Down

0 comments on commit fc5b2d7

Please sign in to comment.