Am Donnerstag, 30. Mai 2019, 15:50:36 CEST schrieb Jesse Glick:
> On Thu, May 30, 2019 at 9:30 AM Martin Weber
wrote:
> > For my step, the snippet generator prints everything on a single line:
> Because your step is not block-scoped.
Thanks for the clarification.
--
E-Mails sollten Text sein,
On Thu, May 30, 2019 at 9:30 AM Martin Weber wrote:
> For my step, the snippet generator prints everything on a single line:
Because your step is not block-scoped.
> cmakeBuild buildDir: 'build', installation: 'InSearchPath', sourceDir: 'src',
> steps: [[args: 'all']]
Looks fine to me,
Am Mittwoch, 22. Mai 2019, 10:38:29 CEST schrieb Robert Sandell:
> You need a config.jelly (and help-field.html) file for your step and the
> rest should be done for you by magic.
Sorry, if my question was not precise.
For the withEnv step, the snippets generator puts nicely formatted text in the
On Wed, May 22, 2019 at 4:38 AM Robert Sandell wrote:
> the rest should be done for you by magic.
Magic favors the well prepared!
https://jenkins.io/doc/developer/plugin-development/pipeline-integration/
--
You received this message because you are subscribed to the Google Groups
"Jenkins
You need a config.jelly (and help-field.html) file for your step and the
rest should be done for you by magic.
/B
Den tis 21 maj 2019 kl 22:33 skrev Martin Weber :
> Hi all,
>
> I see the snippet generator prints a nicely formatted code for the withEnv
> step.
> How can I tell the snippet
Hi all,
I see the snippet generator prints a nicely formatted code for the withEnv
step.
How can I tell the snippet generator to do that for my pipeline step, too?
Any pointer to docs or code are welcome.
Martin
--
Cd wrttn wtht vwls s mch trsr.
--
You received this message because you
