AWS CodePipeline has introduced new features to support branch-based development and monorepos, providing customers with more flexibility in building their pipelines. The new triggers and execution modes allow for a variety of pipeline designs to accommodate different development strategies.
One example is creating a GitFlow release pipeline, which manages large projects with parallel development and releases using long-running branches. With the new features, you can trigger pipelines from multiple branches, simplifying multi-branch pipeline strategies like GitHub flow.
Another example is running a pipeline on all pull requests (PRs), which is a common practice to catch build and test failures before merging changes. The new features allow you to trigger pipelines for all PRs across branches, helping validate proposed changes before merging.
Finally, you can run a pipeline on a single folder within a monorepo, optimizing pipeline executions to only changes inside a specific folder. This reduces costs, speeds up deployments, and optimizes resource usage for projects within the monorepo.
Overall, these new features in AWS CodePipeline enhance the flexibility and efficiency of continuous delivery workflows, empowering customers to automate their delivery pipelines more effectively.