Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: jgiven-plugin
-
Labels:None
-
Similar Issues:
Description
Extracted from JENKINS-30836:
The path for custom CSS/JS files is confusing as the absolute file path is required (/home/jenkins/jobs/build/workspace/trunk/file.js) there. In contrast, the JGiven result json files path is relative (/trunk/jgiven-reports)
In all other plugins I know, the paths are always relative, so the best solution is to also use relative paths for custom CSS/JS. Maybe it would also nice to support http links.
Code changed in jenkins
User: Stefan Wolf
Path:
src/main/java/org/jenkinsci/plugins/jgiven/JgivenReportGenerator.java
src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customCssFile.html
src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customCssFile_de.html
src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customJsFile.html
src/main/resources/org/jenkinsci/plugins/jgiven/JgivenReportGenerator/HtmlReportConfig/help-customJsFile_de.html
http://jenkins-ci.org/commit/jgiven-plugin/901ec03e0e2adb3f93a8d16cb3068646063bfd25
Log:
[FIXED JENKINS-30981] Custom files are now taken from workspace