Its the usual things: * If you have one copy of those scripts and fix something in one of them, all the jobs get the fix. * If you have one copy of those scripts and break something in one of them, all the jobs get broken. * you are free to add variations
On Thu, Nov 3, 2016 at 2:47 PM, Trever <[email protected]> wrote: > We have our build scripts in a git repository. Currently we have every > one of our pipeline jobs check out the build scripts into the workspace > directory in order to run the scripts. This works fine. > > While reading through some other Jenkins posts, I see that we could > optionally have a job that creates an archive out of the build scripts and > our pipeline jobs could copy those scripts from the archived artifacts. > > Is one method better than the other? Would there be any benefits to doing > it one way over another? > > -- > 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/deeab827-b48e-44ee-848d-5b7061493220%40googlegroups. > com. > For more options, visit https://groups.google.com/d/optout. > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- 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/CAA4vtDSpzhnfCGaxveG0Z76gHMwq6AUWevA3BnkAYwfLqhDCHg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
