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, Dan
Thanks Alex,
I think the replay is probably the better option for me.
C
On Tuesday, 31 October 2017 17:05:14 UTC-5, slide wrote:
>
> There are two things that might make your life easier:
>
> 1) Jenkinsfile, you can put this into your source control and then it will
> be executed as if it were i
> On 31. Oct 2017, at 22:51, Christoph Ruepprich 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 he
There are two things that might make your life easier:
1) Jenkinsfile, you can put this into your source control and then it will
be executed as if it were in the web ui. You just change the option in the
job setup to "Pipeline script from SCM" instead of "Pipeline script". Then
when you push upda
I'm new to Jenkins and am learning how to write groovy scripts for
pipelines. Right now I write my code in VS Code and copy & paste it into
the Jenkins' project, save and build. This gets pretty tedious and time
consuming. Is there a better way to develop scripts without having to
either develo
