Automation of tasks is one thing that I am an advocate of in my development projects. Getting functionality that is repeatable with a low risk of human error for a one time cost is a sound business decision and as a developer, keeps your hands on rolling more code for a greater percentage of your work day. It’s a Win-Win scenario.
The Windows Azure Web Sites team along side the Kudu team have added Continuous Deployment functionality in Windows Azure Web Sites with support for three familiar social source code repositories: CodePlex, GitHub and BitBucket. The team has also added support for Contiguous Integration using Team Foundation Service [a new Cloud Based offering of Team Foundation Server].
Windows Azure Web Sites now allows Continuous Deployment from Private Repositories from both GitHub and BitBucket.
In this post:
- Create a Windows Azure Web Site
- Enable Git Deployment
- Associate a Source Code Repository
Create a Windows Azure Web Site
To avoid reinventing the wheel, you can follow instructions outlined on the Windows Azure Develop Center on how to Create a Windows Azure Web Site and Enable Git Deployment.
NOTE: If you do not need a MySQL database, or have decided to go with another database option, choose Quick Create from the Web Site menu instead of Create with Database.
Associate a Source Code Repository
In order to facilitate the Continuous Deployment it’s necessary to have a centralized location to pull the website code from, in this particular blog entry we’re going to use GitHub and BitBucket.
Initializing a Git Repository will redirect the Management Portal to the DEPLOYMENTS tab.
Now that Git has been enabled use the collapsible menus to select how you would like to deploy code to the new Windows Azure Web Site.
Associate a GitHub Repository to Windows Azure Web Sites
Expand the item labeled Deploy from my GitHub repository.
Click on Authorize Windows Azure. This will open a window to federate with GitHub, you will need to approve the ability for Windows Azure to access your GitHub account.
Once access has been granted, the browser will redirected back to the Management Portal to a screen to select either a Public or Private repository.
After selecting the repository to be published, click on the check mark to start the deployment process.
If your repository is empty, push to GitHub to trigger deployment to Windows Azure.
Each subsequent push to GitHub will trigger a service hook and begin a deployment of the latest bits to the Web Site. Now that the deployment has been pulled into the Web Site, clicking on Browse in the Taskbar Drawer will launch the web application.
Associate a BitBucket Repository to Windows Azure Web Sites
Just like associating a GitHub account to a Windows Azure Web Site, expand the Deploy from my BitBucket repository. Authorize Windows Azure to access a BitBucket account by federating authentication through BitBucket.
After clicking on Authorize Windows Azure, a prompt to authenticate with BitBucket.
After signing into BitBucket a prompt to select the Public or Private repository to deploy to Windows Azure Web Sites.
Unlike GitHub, BitBucket will require you push a change to the repository before the Service Hook will deploy code to the Windows Azure Web Site.
Once a push has been made to the private BitBucket repository, the deployment will be pushed to the Web Site.
In the taskbar drawer at the bottom of the browser viewport, click the Browse Button.
A new window will open and the site will display the web files which were pulled into the Web Site.
Continuous Deployment is a great way to introduce new features or functionality to your customers in an automated fashion. With the new support for Private Repositories, Windows Azure Web Sites can help delivery stunning web sites which utilize either open source projects from public repositories, or provide clients with a customized solution from a private repository.
Stay Cloud my Friends…