1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 4 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 mesi fa