-
Bug
-
Resolution: Fixed
-
Minor
-
jenkins-2.375.1 and later
-
-
2.393 and 2.387.2
We use the pluginManager API to automate plugin updates on all of our Jenkins instances. This worked really well for a long time. Since a few weeks it stopped working.
When sending a POST request to /pluginManager/installNecessaryPlugins with the plugins to be updated it gets redirected to /updates/ with status 404.
I'm sending the request like this:
curl --request POST \
--url http://localhost:8080/pluginManager/installNecessaryPlugins \
--header 'Authorization: Basic <redacted-token>' \
--header 'Content-Type: application/xml' \
--data '<jenkins><install plugin="mattermost@3.1.2"></install></jenkins>'
And I get this response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404 Not Found</h2>
<table>
<tr><th>URI:</th><td>/updates/</td></tr>
<tr><th>STATUS:</th><td>404</td></tr>
<tr><th>MESSAGE:</th><td>Not Found</td></tr>
<tr><th>SERVLET:</th><td>Stapler</td></tr>
</table>
<hr/><a href="https://eclipse.org/jetty">Powered by Jetty:// 10.0.12</a><hr/>
</body>
</html>
Did anything drastically change in the API? From the docs and release notes i couldn't figure out if something has changed.
Looking forward to an answer on this.
You might check if you're using a reverse proxy and something has changed in the configuration of the reverse proxy. If that doesn't work, you could compare the differences in the source code between the versions that were working before and the current versions, in case there is something in those changes that might hint at a difference. I'm not sure that others will be able to help you without a way to duplicate the problem in their environment.