-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
Currently the exclusion plugin forces each job to define which exclusion resources it wants to define and use. This can be problematic when multiple jobs want to make use of the same exclusion resources because the user has to take care to add the same exclusion resource to all relevant jobs (duplication), and to try and avoid human error like typos and the like which could result in new exclusion resources being created inadvertently.
What I would prefer to see is if the exclusion plugin provided some configuration options in the global Jenkins configuration area which would allow one to define their exclusion resources globally, and then perhaps provide a drop-down list of available exclusions when configuring each job. This would avoid the duplication and human errors just described.