You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow PDKPipelineProjects to create and destroy pipelines as git branches are created and destroyed. Alternatively, enable additional pipelines tied to a branch per developer.
Use Case
When developing as a team, we often work on different features in branches. We need to test deployments before merging to the main branch, so we currently deploy manually to our individual accounts. This will allow us to test by pushing a commit without impacting the main branch or our teammates' work.
Proposed Solution
Amplify's CI/CD monitors the creation and deletion of branches to create new environments with their own pipelines. PDKPipeline could create and eventbridge rule to trigger pipeline stack creation and destruction when codecommit branches are created and destroyed.
If your team follows [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow),
the pipelines module can optionally help you create independent environments to test and validate
changes before merging. When you create a new branch, it will automatically create a new pipeline
stack and any stages you configure. Once you have finished testing and delete the branch, it will
automatically clean up the stacks created in the branch's environment.
EventBridge Rules trigger Lambda functions on CodeCommit repo branch creation and deletion. The
Lambda function for creation sets the `BRANCH` environment variable and runs a CodeBuild project
that creates the pipeline stack for the branch. It is up to the developer to give their pipeline
stack and stages unique names per branch. The examples show how to use the `BRANCH` variable to do
so. The multi-branch stacks are tagged with the branch name and repository name. The Lambda for
branch deletion lists all stacks matching those tags and deletes them.
I tested this change using a Typescript pipeline project.
This is a cleaned up version of PR #364 due to structural changes during development.
Resolves#302, replaces #364
Describe the feature
Allow PDKPipelineProjects to create and destroy pipelines as git branches are created and destroyed. Alternatively, enable additional pipelines tied to a branch per developer.
Use Case
When developing as a team, we often work on different features in branches. We need to test deployments before merging to the main branch, so we currently deploy manually to our individual accounts. This will allow us to test by pushing a commit without impacting the main branch or our teammates' work.
Proposed Solution
Amplify's CI/CD monitors the creation and deletion of branches to create new environments with their own pipelines. PDKPipeline could create and eventbridge rule to trigger pipeline stack creation and destruction when codecommit branches are created and destroyed.
Other Information
Blocked by #239
Acknowledgements
PDK version used
0.14.8
What languages will this feature affect?
No response
Environment details (OS name and version, etc.)
MacOS
The text was updated successfully, but these errors were encountered: