On Thu, 2018-05-03 at 16:26 +0000, Mark Waite wrote: . . .It seems like you're describing a very good use case for a Pipeline shared library. Each repository and each branch then has a very simple Jenkinsfile which loads the shared library and calls it. That's the technique used for Jenkins plugin development<https://github.com/jenkinsci/git-client-plugin/blob/master/Jenkinsfile>
Correct me if I am mistaken, but that would imply that I would still need to insert an identical Jenkinsfile into 155 projects in order to actually use the @library. That's not improving anything. I want to specify the Jenkinsfile from a different git repo and not alter all the other 155 repos, and there is no means of doing this as the pipeline plugins are currently written. That should be a base use-case, and it seems to have been missed. As a result, every project build that is changed over to pipelines needs to be modified for very questionable reasons. -- 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/1525371033.24903.14.camel%40esentire.com. For more options, visit https://groups.google.com/d/optout.
