Most of our jobs use a bunch of common shell functions which are sourced at the beginning of the job. Currently these shell functions are in a separate repository. Since it's a pain to check out more than one repository per job, I though about moving the shell function into a global shared pipeline library which is loaded via @Library in the Jenkinsfile (we already have such a library). However, afaik the library is only checked out on the master and is not available on the slaves, i.e. I cannot source any include files in shell script commands. Is there any other convenient way to use a set of common files across many jobs and slaves?
-- 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/2629c793-8d18-4599-897f-fd3b46394585%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
