pipeline: script location

30 views
Skip to first unread message

Kenneth Johansson

unread,
Apr 26, 2017, 7:01:28 AM4/26/17
to Jenkins Users
So I have a pipeline job that is using the "pipeline script from SCM" as
suggested in the documentation.

But for developing code this is really really annoying as I now need to
checking every single change even if its just to test something out and
for a new user its going to be quite a lot of test as its not really
very clear how to write this pipeline groovy scripts.

So I thought that just having the script in the jenkins web interface
would be easier for testing and that works if you just want to do an
echo but you lose the git connection to your project so your stage
section can simply not compile your project.

How do people develop pipeline scripts ?? I must be missing something
obvious.


Mark Waite

unread,
Apr 26, 2017, 7:36:14 AM4/26/17
to Jenkins Users
There is a "Replay" link attached to each build that will allow you to make experimental changes in an editor on the web page.  For example, I see "Replay" above the "Pipeline Steps" link in the drop down menu associated with Build #1 of one of my pipeline jobs that uses Pipeline definition from SCM.

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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d18f3728-daaa-468d-fc4d-030a207becf2%40inteno.se.
For more options, visit https://groups.google.com/d/optout.

Kenneth Johansson

unread,
Apr 26, 2017, 8:03:14 AM4/26/17
to jenkins...@googlegroups.com
On 2017-04-26 13:35, Mark Waite wrote:
There is a "Replay" link attached to each build that will allow you to make experimental changes in an editor on the web page.  For example, I see "Replay" above the "Pipeline Steps" link in the drop down menu associated with Build #1 of one of my pipeline jobs that uses Pipeline definition from SCM.

Mark Waite
I tested this and It did work for the stages section but not for the parameters. Looks like the parameter section is ignored completely on replay. Might be more useful later when I managed to get past the basic configuration step.
 

On Wed, Apr 26, 2017 at 5:01 AM Kenneth Johansson <kenneth....@inteno.se> wrote:
So I have a pipeline job that is using the "pipeline script from SCM" as
suggested in the documentation.

But for developing code this is really really annoying as I now need to
checking every single change even if its just to test something out and
for a new user its going to be quite a lot of test as its not really
very clear how to write this pipeline groovy scripts.

So I thought that just having the script in the jenkins web interface
would be easier for testing and that works if you just want to do an
echo but you lose the git connection to your project so your stage
section can simply not compile your project.

How do people develop pipeline scripts ?? I must be missing something
obvious.


--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d18f3728-daaa-468d-fc4d-030a207becf2%40inteno.se.
For more options, visit https://groups.google.com/d/optout.
--
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-use...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages