Hi,
It may not be the best or most elegant, but this is what I do:
(1) I use vim to edit the script.
(2) For testing, I create a pipeline job, paste the script into the*
Pipeline script *entry field, and run the job.
(3) When I am done, I check the script into git, and reconfigure the job
to use *Pipeline script from SCM*.
(4) I often have to re-run the script multiple times, and approve
functions in *In-process Script Approval*
do to the security sandbox.
--
Craig
On Tue, Feb 2, 2016 at 2:14 PM, Tom Kierzkowski <
thomas.kierzkow...@gmail.com> wrote:
Hello! I'll try to break out the question in different parts.
>
>
> - What IDE development setup are you using to
> create/configure/maintain your Pipeline scripts?
> - How do you test your scripts within your IDE/development setup?
> - Any specific resources for setting up a development environment for
> IntelliJ IDEA (Not married to it, but has more features than Vim :))
>
>
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVf3OXJ16aR4b-f6kvLu5ZnuLQQ5-rzpLDyMaiQeL%3DdUTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
