I have followed this guide:
It mentions that it will push the default branch from GitHub.
What about all the other branches one might have in the same repo?
Can I somehow specify which branch to deploy?
Add a comment
|
2 Answers
Here is how you can accomplish branch-specific deploy scenarios using AWS Code Deploy and AWS CodePipeline:
- Assuming you've already set up an application and deploy group with Code Deploy, create one group for your "Dev" branch, and another deploy group for "qa" or "stage".
- Enable CodePipeline in your AWS Console.
- Create a new pipeline by authorizing your Github account and providing access to the repository and branches you desire.
- In the BETA section of your new pipeline, edit it, authorize github again, and choose the specific branch you wish to deploy when changes are made.
- Now your system will automatically deploy based on a specific branch.
Comments
After scratching and cursing and researching and out of the box thinking...I managed to do it like this.
As long as CodeDeploy plays nicely only with the default branch, let's manipulate that one from the GitHUb API [you can do it also from the settings of the GH UI].
This is the code to change/update the default branch from your repo.
I have confirmed that CodeDeploy had no problem deploying the new branch! :]
1 Comment
Noel Baron
I don't think this is the right answer. I'm also new to Code Deploy and was disheartened to find that I cannot set up deployment groups using my Dev or Stage branches. Ideally, the solution is to be able to say: Dev Branch -> Deploy to Dev Group. Stage Branch -> Deploy to Stage Group. Prod Branch -> Deploy to Prod Group.