Deprecated Plugins can give 403 errors

[halkeye]

For example https://plugins.jenkins.io/azure-iot-edge/ gives an nginx 403 forbidden error. Our unverified guess is that the directory exists, but the file got deleted when the plugin was removed.

Easiest solution, process https://github.com/jenkins-infra/update-center2/blob/master/resources/deprecations.properties and create a depreciated page and use the link in the properties file if available.

Recommendation from writer:

• Create new JenkinsPluginDeprecations in https://github.com/jenkins-infra/plugin-site/blob/master/plugins/gatsby-source-jenkinsplugins/utils.js
• Create new page similar to

  plugin-site/gatsby-node.js

  Lines 56 to 61 in adfee9e

  	createPage({
  	path: `/${edge.node.name.trim()}/`,
  	component: pluginPage,
  	context: {
  	name: edge.node.name.trim()
  	}