-
Bug
-
Resolution: Not A Defect
-
Major
-
Jenkins - 2.61
Config File Provider Plugin - 2.15.7
Maven Integration Plugin - 2.15.1
Exceptions and stack traces are thrown in the Jenkins log when I attempt to visit
- Manage Jenkins -> Global Tool Configuration, or,
- Manage Jenkins -> Managed Files
Within Jenkins I see the following behavior:
- In the Global tool configuration a stack trace is displayed in the "Maven configuration" section of the page.
- In the Managed files I do not see any files or entries listed.
- This also affects the job configurations that support a maven build action, since I am not able to select a managed maven settings file.
This issue should be closed. I discovered after some trial and error that one of the entries in the org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml file was invalid (did not have a providerId node).
Once I removed it from the file, my errors went away and I was able to view the managed files.