Someone here at the company wrote a "System Groovy Script" that runs as a nightly job on master. The code of the script, all 100 lines of it, is directly in the job configuration in the web interface. I would like to get that code in a git repository, so that it's easy to roll back if needed, and also so that it is easier to read and write when I have the code open in IntelliJ. What would be a "best practice" to do that?
I see that the Groovy plugin has only two options: * code directly in the job config * a groovy file, I assume somewhere in the job workspace, but that isn't specified. Would I need another configuration before that? In "Source Code Management"? How would you do it? -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b5a6dc9d-0976-469c-8ae3-c17aaff05427n%40googlegroups.com.
