You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jimklimov opened this issue
Aug 1, 2019
· 2 comments
Labels
TriageNeed to clarify, remove, close or whatever to clean up open issues / PRsuiFeatures that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)
One technically plausible way to edit lockable resource assignments is to change the strings in the Jenkins master global configuration page, in the section to list and otherwise edit these resources.
One discomforting thought nags at me however: does this mean that if an administrator takes some time to edit the global configuration (anything, not necessarily the resources) and then saves (or applies) it, would the (not-edited) string values from the resource list be re-applied to the actual resource objects? Or is there some tracking of "this field was not touched, do not re-apply"?
What I am concerned about is the possible re-assignment of resources that have been grabbed (or released) by builds and users between the time an administrator opened their $JENKINS_URL/configure page and the time they ultimately saved it... perhaps re-setting back the resource allocation statuses... is there something to worry in practice?
The text was updated successfully, but these errors were encountered:
That is the reason, why I want to remove the file 'reservedBy' from config page. More sense has a reason why user reserve the issue. Similar to node disconnect (or temporary disconnect) reason.
TriageNeed to clarify, remove, close or whatever to clean up open issues / PRsuiFeatures that may impact UI, pages made by the plugin or external UIs (BO, legacy, etc.)
One technically plausible way to edit lockable resource assignments is to change the strings in the Jenkins master global configuration page, in the section to list and otherwise edit these resources.
One discomforting thought nags at me however: does this mean that if an administrator takes some time to edit the global configuration (anything, not necessarily the resources) and then saves (or applies) it, would the (not-edited) string values from the resource list be re-applied to the actual resource objects? Or is there some tracking of "this field was not touched, do not re-apply"?
What I am concerned about is the possible re-assignment of resources that have been grabbed (or released) by builds and users between the time an administrator opened their
$JENKINS_URL/configure
page and the time they ultimately saved it... perhaps re-setting back the resource allocation statuses... is there something to worry in practice?The text was updated successfully, but these errors were encountered: