IMO it's a good thing to have a job per repo/project. You could probably have a look at either Job DSL plugin to version and script the fact and jobs are alike. Or use a pipeline script for all of them, using by default a standard function coming from the Pipeline Global Library Plugin.
My 2 cents Le 17 août 2016 3:25 PM, "Pykler" <[email protected]> a écrit : > We have a code base with many small repos, each repo is essentially a > service. To test we have separate builds for each small repo, yet they are > all pretty much identical. The problem happens when we want to make a > change, we have to change every single one (over 60 builds). Is there a way > we can have a single set of build steps that run regardless of the repo > that was changed? does anyone have a similar setup and can share the best > practices > > -- > 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/b7dd8d3d-9d39-47fa-8f3c-2928bbe734fe%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/b7dd8d3d-9d39-47fa-8f3c-2928bbe734fe%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CANWgJS4evLd2N0-2m8Oeh-_gUO04k_Mw4_xoLqp5NXSz4dXO0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
