manage.jelly:46:53:

[email protected] (JIRA) Sat, 26 Oct 2019 08:35:07 -0700

Title: Message Title

Daniel Beck commented on

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:

 
                                                                ManagementLink.all()  
                                                            

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.

Add Comment

This message was sent by Atlassian Jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201280.1565796626000.2424.1572104043559%40Atlassian.JIRA.

[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53:

Reply via email to