[JIRA] (JENKINS-59150) Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information

4 views
Skip to first unread message

cimpoiesgeorge@gmail.com (JIRA)

unread,
Aug 30, 2019, 8:38:02 AM8/30/19
to jenkinsc...@googlegroups.com
George Cimpoies updated an issue
 
Jenkins / Improvement JENKINS-59150
Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information
Change By: George Cimpoies
Summary: Upgrading to Jenkins LTS 2.176.x documentation has logs about the new Stapler routing rules have erroneous information
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

dbeck@cloudbees.com (JIRA)

unread,
Sep 4, 2019, 9:26:02 AM9/4/19
to jenkinsc...@googlegroups.com
Daniel Beck closed an issue as Won't Fix
 

Don't use a gerrit-trigger version that has been obsolete since February.

Change By: Daniel Beck
Status: Open Closed
Resolution: Won't Fix

dbeck@cloudbees.com (JIRA)

unread,
Sep 4, 2019, 9:31:01 AM9/4/19
to jenkinsc...@googlegroups.com
Daniel Beck commented on Improvement JENKINS-59150
 
Re: Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information

And regarding the reported problem here, there isn't one either.

The complete log messages read:

Sep 04, 2019 1:27:20 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onDispatchTrigger
New Stapler dispatch rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement serverStatuses". Learn more: https://jenkins.io/redirect/stapler-facet-restrictions
Sep 04, 2019 1:27:20 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger
New Stapler routing rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses". Learn more: https://jenkins.io/redirect/stapler-routing

These are two different messages, for two different potential ways the request could be routed:

The warnings are logged in the order they are attempted, first the view, then the getter. Everything here works as intended.

Reply all
Reply to author
Forward
0 new messages