3 ms·
It's much worse; it's very difficult to debug complex pipelines (you can never get "inside" the runner), there are no services or reuse etc. Due to lack of fea
by zxcmx 6y ago
It's much worse; it's very difficult to debug complex pipelines (you can never get "inside" the runner), there are no services or reuse etc.
Due to lack of features you can really only use codepipeline in very simple cases for builds. Just too painful.
So it's better to stick to codepipeline for deployments only; but if you do, your deployment ci is now different than your build ci.
Really wanted to like it (the security benefits are real) but now avoid and use "full" ci for everything.
Obviously org, team and situation dependent, but we got the most velocity benefit from using 1 tool everywhere. If you had to use 1 tool I can almost guarantee you would not choose codepipeline after using it.