Number of pipelines recommended in CodePipeline

Question

Hi,

I'm using TeamCity to deploy on ECS and considering moving to CodePipeline. I'm wondering if I should have just one or two pipelines. Here is my current scenario.

Pipeline 1
This pipeline is meant to build the Docker image and push to ECR.

Pipeline 2
This pipeline is meant to deploy the new docker image creating a new task definition and making the deployment.

To me both approaches look fine. The only advantage that I can see having two pipelines is that you could make a deployment running a pipeline instead of using any other tool like CFN.

Any other differences I'm missing?

Thanks

Accepted Answer

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.

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.

Number of pipelines recommended in CodePipeline

Relevant content