Hi, I’ve been looking at using the Environments functionality in Go 2.1 and I'm a bit alarmed at how many more Pipelines it looks like I’ll have to define.
Currently we have a combination of 27 applications and libraries, making up 27 different pipelines.
Each application pipeline is defined as such:
build -> dist -> deploy-dev -> deploy-sys -> deploy-uat -> deploy-preprod -> deploy-production
Now to use the Environments page it seems that I’ll have to split out the deploy stages into separate pipelines, each with one stage, in order to assign each to their respective environment.
Build -> dist
So that’s six pipelines for each application, making a total of 162 pipelines for all 27 applications and libraries, which seems like a lot to have to manage on one server.
Is there another way to use the Environments without having to do this and define so many pipelines? Or is there a better way I should be defining my pipelines? I was thinking that maybe we should have another Go Server and split our appliciations across two servers but that also seems to be increasing the maintenance overhead.