search

griddynamics / mpl

[IT-36925] Jenkins Shared Modular Pipeline Library
https://blog.griddynamics.com/developing-a-modular-pipeline-library-to-improve-devops-collaboration/
Apache License 2.0
156 stars 97 forks source link

Real examples of file names for modules #73

Closed ctran closed 4 years ago

ctran commented 4 years ago

I would like to see real examples of the stage names and the module hierarchy if you're willing to share.

Thanks.

sparshev commented 4 years ago

Hi @ctran,

So I can't share the customer's pipeline structure, but you can check the half-completed real-example example-cicd nested library - the names in it is based on the real project automation and the vars/ExampleProjectPipeline.groovy definition are quite the same as the one was used.

Unfortunately I'm stuck with the docker certificates for this example, but hopefully will find some time to find a way and complete it.

Overall I'm trying to keep it simple for every project - and since they are usually microservices - the logic is not very complex. The only thing is with build version generated automatically and the deployment procedures should use the right helm packages.

Thank you

ctran commented 4 years ago

I've looked at those. They are pretty small set, I'm hoping to see a bigger list to compare with what I need to do.

I appreciate you taking time answering my query, however.

sparshev commented 4 years ago

Sorry, @ctran - the MPL is not an automation solution database. It's a framework to simplify build your own solutions and what we have right now - that's the only thing I can share as open source.

If you need some extra expertise for your company projects - I can only suggest to contact Grid Dynamics for any professional support.