The buggy file is no longer part of the website, the reported exception does not appear in any of the current pages. There seems to be a deploy problem though: WEBSITE-630

Doesn't that also indicate that there is a problem somewhere that the workflow-cps plugin which provides the parallel step and the load step is no longer documented in the pipeline steps files generated for jenkins.io?

Other "internal" steps (like stash, sleep, sh, bat, and node) are documented in workflow-basic-steps and workflow-durable-task-step.

It certainly seems like an error that the site deploy does not remove deleted files (as described in WEBSITE-630).

It also seems like an error that the workflow-cps plugin provides two crucial steps (load and parallel) which are not documented on the generated site. I assume they were generated previously but are no longer generated, or the generator is failing to generate them but instead of writing the file with the No DataBoundConstructor error, it removes the generated file.

Since the git plugin generated page is the current "winner" of most voted "Not helpful", I'll need to learn how those pages are generated in order to improve the documentation of the git step. More to do...

Maybe
https://ci.jenkins.io/job/Infra/job/pipeline-steps-doc-generator/
should generate a list of steps that don't support documentation?

To test he PR one can download the allAscii zip from https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fpipeline-steps-doc-generator/detail/PR-17/2/artifacts ,

unpack it in /content/doc/pipeline/steps of jenkins.io repo, temporarily remove the part of the fetch script and use

make run 

Mark Waite I think this works fine now, please check and feel free to close the ticket / add more suggestions

https://jenkins.io/doc/pipeline/steps/workflow-cps/

Thanks very, very much Zbynek Konecny!