Good one Muthu, eagerly waiting for more articles sharing your vast experience in AWS.
One doubt on this, can you share a use case where we need couple of build levels (one at CodePipeline level and another at CodeBuild triggered by Step Function)?
Hi Ashok, CI pipelines are predefined and actions defined are static. With just codepipeline, every stage would execute as it is defined. A shared repo which has pipeline setup to do more than one build based on folder paths within the repo, all folders would get built or deployed even when files in one or few folders are updated. Step Functions can help in such cases to skip or execute stages conditionally
Good one Muthu, eagerly waiting for more articles sharing your vast experience in AWS.
One doubt on this, can you share a use case where we need couple of build levels (one at CodePipeline level and another at CodeBuild triggered by Step Function)?
Hi Ashok, CI pipelines are predefined and actions defined are static. With just codepipeline, every stage would execute as it is defined. A shared repo which has pipeline setup to do more than one build based on folder paths within the repo, all folders would get built or deployed even when files in one or few folders are updated. Step Functions can help in such cases to skip or execute stages conditionally
Something like this Ex: 1
Will also help in complex pipelines where some stages/actions need to be executed/skipped on conditions and like this Ex: 2