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 On Tuesday, October 25, 2016 at 2:26:37 PM UTC-7, Sam K wrote: > > 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? > -- 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/3ad861c9-8781-4657-8e5c-4e4f455dd1c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
