Using Cucumber Living Documentation Plugin, only the first asciidoc line is rendered
See original GitHub issueHi there,
I’m trying to use cukedoctor via the Jenkins plugin “Cucumber Living Documentation Plugin”. However, only the first line with asciidoc markup is rendered as expected. The second line is left as-is and any following markups in the feature file are ignored. For example, if I have a feature file that begins with:
# language: sv
# encoding: utf-8
Egenskap: Beslut om insats
<1> First line
<1> Second line
renders as:
I’ve tried to figure out why, but unfortunately I have not found any solution. I would be so grateful if you could help me out.
Jenkins version: 2.176.2 Cucumber Living Documentation Plugin version: 2.2.2
Best Regards, Magnus Axelqvist
Issue Analytics
- State:
- Created 3 years ago
- Comments:49 (24 by maintainers)
Top Results From Across the Web
Cukedoctor - GitHub
This module brings the ability to execute Cukedoctor converter through a maven plugin. The plugin just scans .json cucumber execution files in target...
Read more >Cukedoctor Documentation
Cukedoctor is a Living documentation tool which integrates Cucumber and Asciidoctor in order to convert your BDD tests results into an awesome documentation ......
Read more >Living Documentation Plugin | Cucumber for JIRA
Generate your product documentation using a common business language improving collaboration amongst all team members. Integrate with CI & Git. Integrate ...
Read more >Editing with live preview - Asciidoctor :: Discussion
I put together a short guide that steps through setting up a live web preview of the HTML generated from your AsciiDoc document...
Read more >2013 - One Jar To Rule Them All
Documentation is a Living System with Asciidoctor ... The plugin renders all AsciiDoc files that are at src/main/resources folder and its ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ to start with.
Hey guys,
This is something related to Jenkins way of loading plugins and it’s dependencies, for example if I run this integration test (also this one) everything works. Note that integration tests spin up a Jenkins instance and deploy the plugin there.
For some reason it worked with previous jruby (1.7.x) but when we upgraded to 9.x it stop working and new Asciidoctor requires JRuby 9.
I tried a lot of dependency version “constellations” (jruby/asciidoctorJ/Jenkins) without success.
@headius if there’s any way to debug this, let me know.
On my side, I still have to try the latest asciidoctorJ and JRuby, probably this weekend I have some results to share.
Thank you guys