1 個回答
- 最新
- 最多得票
- 最多評論
0
We typically recommend one pipeline per service or shared component, for ECS that means that unless you're building and image that is used by multiple TaskDefinitions, I'd recommend build and deploy in the same pipeline, there's simply no advantage in splitting that pipeline in two, even if you want to control when to deploy the image you can disable the transition or add a manual approval step.
The less resources you own the less your ops costs.
But I also need to say that if you want to use two pipelines for some other reason (maybe finer permission control), it should work equally well.
已回答 4 年前
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前