Hi Martin,
This (markup rendering) works fine for me (with HTML markup used in
“vars/foo.txt”); of course only once the build succeeds; but I guess you have a
different problem (than non-successful builds), because otherwise it does not
change at all or is rendered at all.
Maybe it also depends on markup formatter setting? E.g. via JCasC:
Jenkins:
…
markupFormatter:
rawHtml:
disableSyntaxHighlighting: false
…
HTH Reinhold
From: [email protected] <[email protected]> On
Behalf Of Martin d'Anjou
Sent: Samstag, 19. Oktober 2019 01:00
To: Jenkins Users <[email protected]>
Subject: Re: Whats is the format for custom pipeline library help files?
Thank you Mark, this is a good set of examples.
But :-( it does not work. The markup is rendered verbatim, that is, it is
treated as a plain text file.
And even when I add the jenkins-infra/pipeline-library to my jenkins instance,
it shows the help files as text, there is no rendering of the markup.
It is not a critical thing.
Best,
Martin
On Friday, October 18, 2019 at 6:23:08 PM UTC-4, Mark Waite wrote:
https://github.com/jenkins-infra/pipeline-library/tree/master/vars seems to
include HTML markup in the txt file. For example, runATH.txt starts with:
<p>
Runs the <a
href='https://github.com/jenkinsci/acceptance-test-harness'>Acceptance Test
Harness</a> in a configurable way
</p>
On Fri, Oct 18, 2019 at 4:03 PM Martin d'Anjou
<[email protected]<javascript:>> wrote:
Hello,
We can write documentation for pipeline library in files like vars/foo.txt and
resource/org/foo/bar.json, but I would like to know what format and markups are
supported.
I found the help for the docker pipeline plugin, but it's written in
jelly<https://github.com/jenkinsci/docker-workflow-plugin/blob/6e99c93105d9fb1f2c7b2ee4896ee8f23cd98233/src/main/resources/org/jenkinsci/plugins/docker/workflow/DockerDSL/help.jelly>
and after trying, jelly is not a supported format for the help files.
Thanks,
Martin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected]<javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/73becfdb-b513-450b-af2d-5822ef259e86%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/73becfdb-b513-450b-af2d-5822ef259e86%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Thanks!
Mark Waite
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/e7e88232-fcb2-4145-96a3-5c22ffc995a8%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/e7e88232-fcb2-4145-96a3-5c22ffc995a8%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/AM0PR01MB6147A9A8A1D5CE76E27C3EC5F7680%40AM0PR01MB6147.eurprd01.prod.exchangelabs.com.
