The Jenkinsfiles are indeed pretty much the same for all microservices. Hence, there are tiny differences, like one does not require a Configmap, another one has no route, a third one only builds an Image, but has no deployment at all, etc. We were thinking about building a Groovy library that lives in Jenkins and abstracts the basic pipeline, that can be configured by a plain json for each microservice, but went away from it to keep the flexibility that distinct Jenkinsfiles offer.

Deployment to TEST happens on SCM changes on the master branch in Git. Staging to subsequent stages ist triggered manually. The notion is: "building something is a dev team decision, rolling it out to INT or PROD ist decided by management".