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:
MyApp1_Pipeline
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.
E.g.
MyApp1_Pipeline
Build -> dist
Dev
===
MyApp1-Deploy-dev_Pipeline
deploy-dev
Sys
===
MyApp1-Deploy-sys_Pipeline
deploy-sys
Uat
===
MyApp1-Deploy-uat_Pipeline
deploy-uat
PreProd
======
MyApp1-Deploy-preprod_Pipeline
deploy-preprod
Production
========
MyApp1-Deploy-production_Pipeline
deploy-production
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.
Thanks
Andy Birchall
Environments require many more pipelines
Comments
2 comments
I have the same question. Can someone from thoughtworks comment on this?
Thanks,
-russ
what about templates?
We have the same situation (luckily with a lot fewer projects needing to be build for now), and using 1 group for all pipelines of a project for, and environments - gives cross segmentation of pipelines.
There was a discussion on a "meta-pipelines", where "sub-pipelines" can be grouped across environments, but there is nothing available on this yet....
Please sign in to leave a comment.