As a further diagnostic tool we can mess with the internals of your test instance a bit. /script is the URL of the script console (docs: https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console ) This will tell you all known links showing on the "Manage Jenkins" screen:
The following will temporarily (until restart) remove a link from that screen (and basically remove its functionality – depending on the link, some things will just be unavailable, e.g. the Global Security Configuration is implemented like that):
ManagementLink.all().remove(0)
(0 is the first entry in the list, and it's ordered the same way as they show up on the screen, i.e. System, Security, Tools, …). I wonder whether you could use this & a few restarts as needed to determine the culprit(s). That said, this looks like a very weird issue. Perhaps a problem around Tomcat? If that bundles Groovy, for example, and its Groovy takes precedence over Jenkins', that would be a potential problem. |