RepositoryBrowser.getChangeSetLink exceptions from Jelly pollute log

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Your Jenkins log can fill up with long stack traces like

      h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: browser.getChangeSetLink(cs) in /jenkins/job/.../1234/. Reason: java.net.MalformedURLException: no protocol: 
java.net.MalformedURLException: no protocol: 
	at java.net.URL.<init>(URL.java:585)
	at java.net.URL.<init>(URL.java:482)
	at java.net.URL.<init>(URL.java:431)
	at hudson.plugins.git.browser.GitRepositoryBrowser.getUrl(GitRepositoryBrowser.java:47)
	at hudson.plugins.git.browser.GithubWeb.getChangeSetLink(GithubWeb.java:40)
	at ...

      when this is a harmless condition: just an unconfigured git repository browser base URL.

      Probably RepositoryBrowser should get a new method that calls getChangeSetLink but logs exceptions at FINE and returns null, and then Jelly views (both in core and plugins) should be updated to use it. (Falling back to displaying an unlinked changeset, just as if getChangeSetLink returned null.)

            Assignee:
            Unassigned
            Reporter:
            Jesse Glick
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: