Plugin page not found [https://plugins.jenkins.io/markdown-params/](markdown-params)

[jesusnoseq]

Service(s)

plugins.jenkins.io

Summary

I have developed a new Jenkins plugin https://github.com/jenkinsci/markdown-params-plugin
And I am having an issue with the doc page.
While I can see it when searching for it on the Jenkins plugin site https://plugins.jenkins.io/ui/search/?query=markdown-params, the plugin page itself returns a 404 error https://plugins.jenkins.io/markdown-params/
I am unsure how to fix this issue.
Could you please let me know if there are any hints regarding the possible cause of the issue?
Thank you!

Reproduction steps

Go to
https://plugins.jenkins.io/ui/search/?query=markdown-params
where the plugin is listed and
Open
https://plugins.jenkins.io/markdown-params/
The result page is a 404 error

[github-actions]

Take a look at these similar issues to see if there isn't already a response to your problem:

1. 85% Plugin not found on plugin site #3696

[dduportal]

Quick initial analysis on the infra:

• Tried purging Fastly page (curl -XPURGE <...>) => successful but kept showing an HTTP/404
• The URL https://plugins.origin.jenkins.io/markdown-params/ also shows HTTP/404

=> it is not a caching issue (neither client side or Fastly side)

Continuing by checking the build and deployment logs

[dduportal]

🤦 the plugins site fails to build since October 31:

Which explains why the page is not published

[dduportal]

Update:

• It's only the "Deployment" part which fails, during the azcopy step
  • Same as Javadoc fails to deploy (trusted.ci.jenkins.io) #4378
  • @smerle33 also caught the same error for stats.jenkins.io
• chore(Jenkinsfile) capture azcopy logs when deployment fails plugin-site#1989 to collect the azcopy logs when failing so we can check them right now
• Logs are showing the same error pattern as in Javadoc fails to deploy (trusted.ci.jenkins.io) #4378

The timing of these error, on ALL of our azcopy systems, is suspicious. Of course, it maps to when we deployed the new agent VM/container image 2.10.0 which features a new version of the utility CLI azcopy.

This new version, https://github.com/Azure/azure-storage-azcopy/releases/tag/v10.27.0, features changes related to creating folders and parallelization: looks like a good culprit...

We are trying with manual replay of pipelines using the previous azcopy version: if it work, we'll revert to the old version (and report back to Microsoft).

[dduportal]

Update:

• Retrying with the previous version of azcopy did fix the error: your page is now visible

Next steps:

• Revert azcopy version to our infrastructure
• Checks that it solves all deployment issues