-
Bug
-
Resolution: Fixed
-
Minor
-
None
My markdown description files have many references to environment variables with backticks around them (as it explains the jenkins job scripts themselves, which use environment variables).
While I'm sure I could ask devs to escape any comments they make, it's confusing to have a build fail for something in the meta-docs. It would be great if I could just disable token macro parsing at global- or job-level.
Thanks!
OK. Seems the fix that would all escaping of Token Macros happened in Feb 2012, but no release yet
https://github.com/jenkinsci/token-macro-plugin/compare/da2858d...38919bf
So it seems that any "$" in descriptions will fail the build, so a toggle in project-description-setter would be AMAZING
Thanks!