Pipeline development small window

15 views
Skip to first unread message

Sam K

unread,
Oct 25, 2016, 5:26:37 PM10/25/16
to Jenkins Users
As the pipeline code gets more and more complicated, I find the tiny window to do the coding very painful.  So, I've been copying and pasting changes from Notepad+/gvim, hit 'Apply', make sure there are no errors and then run the pipeline.  

Is there a better way other than checking this into source control and doing the changes from eclipse or some IDE?  I don't want to clutter all the git logs with these pipeline changes.

Is there going to be a change that will allow making the pipeline window bigger at least?  

Michael Lasevich

unread,
Oct 25, 2016, 6:27:55 PM10/25/16
to Jenkins Users
You can/should keep it in Git but you can use the "Replay" function to test your modifications before committing them (modify in IDE, cut-n-paste to Replay window to test, then commit when ready).

I am not sure why you would want to keep it out of git log, that is exactly what git log is there for - but you can create a branch, work your changes there, then commit as a single change to your normal branches

Lastly, you may want to look into Global Libraries - you can keep those in a separate Git Repo, so depending on your needs, this may be one solution.

HTH,

-M
Reply all
Reply to author
Forward
0 new messages