Searching Better Handling with Global Maven Settings in Declarative Pipeline
I have following set up in my Jenkins instance (Version 2.240):
A Maven setting.xml is stored in Managed File -> Global Maven Settings.xml. In Managed Jenkins -> Managed Tools, this settings.xml is set in Maven configuration -> Default global settings provider -> Provided global settings.xml.
Unfortunately, with above pipeline script my global set Maven settings.xml isn't used. So my question is, is there a trick that I can say global in my pipeline script or in my Jenkins configuration that which settings.xml should be used without using withMaven?