Jenkins and Asciidoctor integration is not straightforward and always caused issues on every jenkins or plugin update. When we updated Cukedoctor (the library used to generate documentation from cucumber features) to Asciidoctor 2.x the Jenkins plugin simply stopped working because Asciidoctor cannot load ruby gems via JRuby, we tried different approaches without success and now we decided to deprecate this plugin and use another tool to publish the cucumber documentation. Details on this issue: https://github.com/rmpestano/cukedoctor/issues/157
Jenkins and Asciidoctor integration is not straightforward and always caused issues on every jenkins or plugin update. When we updated Cukedoctor (the library used to generate documentation from cucumber features) to Asciidoctor 2.x the Jenkins plugin simply stopped working because Asciidoctor cannot load ruby gems via JRuby, we tried different approaches without success and now we decided to deprecate this plugin and use another tool to publish the cucumber documentation. Details on this issue: https://github.com/rmpestano/cukedoctor/issues/157
The next steps are to follow the process of plugin removal from Jenkins plugin center, described here: https://www.jenkins.io/doc/developer/plugin-governance/deprecating-or-removing-plugin/