- 最新
- 投票最多
- 评论最多
The way that CodePipeline works today each branch would need its own pipeline and each branch would trigger is respective pipeline. So if you push to your test branch codepipline on the main branch should not trigger until you merge changes to the main branch. If you pushed to test and it passed all your tests, you can have a step in codepipeline using codebuild or a lambda invoke step that merges the test branch into Main, which would then trigger that pipeline out to production. You can take a look at this blog post which provides another way to accomplish this and included sample code. You can also look at the preview of CodeCatalyst as well. Hope this make sense and is helpful.
Follow this: https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-trigger-source-repo-changes-console.html.
You will need to setup a cloud watch rule associated to code commit, which then can be customized with either lambda or other integrations.
相关内容
- AWS 官方已更新 9 个月前
You can blame me for this behavior :). I had identified an issue when BitBucket integration was in beta and I wanted to have separate Pipeline in my Development, Staging, and Production environments to match with my branches.