-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Consider the following use case for the external workspace manager plugin: all the nodes have the same mounts as the master node (e.g. in a homogeneous network).
Currently, the 'exws' step looks for the disk definitions in the External Workspace Template (from global config) and the fallbacks to the Node configuration. For this use case, it may be useful to have a second fallback condition: External Workspace Definitions (global config).
So the search order would be: template, node, global.
See the discussions on https://github.com/jenkinsci/external-workspace-manager-plugin/pull/6
[JENKINS-35440] Implement a second fallback when searching for disk definitions
Thank you Martin for adding this comment.
The issue description that I've provided was a bit ambiguous, but your comment makes it more clear.
Thank you for capturing this in Jira Alex. You are very thorough!
In the current design, the user has to provide a global configuration, plus either 1) node configuration, or 2) template configuration. The idea when I suggested the second fallback was that in homogeneous networks, where all nodes have the same mounts as the master node - or in even smaller cases with only a master node, only a global configuration would be needed. This in fact reduces the amount of user configuration, at the cost of some internal complexity, and some additional documentation.