Thanks Daniel, when making changes in replay, is there a way to promote those changes to the actual script, or would I have to copy&paste them?
Will the Jenkins CLI work only for declarative pipeline syntax, or will scripts work, too? Cheers, C On Wednesday, 1 November 2017 08:02:12 UTC-5, Daniel Beck wrote: > > > > On 31. Oct 2017, at 22:51, Christoph Ruepprich <[email protected] > <javascript:>> wrote: > > > > This gets pretty tedious and time consuming. Is there a better way to > develop scripts without having to either develop them in the web UI or copy > & paste them? > > https://jenkins.io/blog/2016/04/14/replay-with-pipeline might also help. > > The declarative pipeline syntax also has a linter accessible from the > Jenkins CLI, which should cut down on the trial & error executions: > https://jenkins.io/doc/book/pipeline/development/#linter > > -- 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/30c0e3a4-aece-4398-9351-fe21d0f886bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
