Windows Azure Websites (WAWS) is a great PaaS service in Microsoft's Cloud Computing platform Windows Azure. It makes it very easy to create, run, and scale web sites or web APIs. The new Team Foundation Services integrate perfectly with WAWS and make it possible to setup a continuous integration environment in the cloud within minutes.
Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Continuous Integration With Windows Azure Websites and Team Foundation Services
1. Continuous Integration with Team Foundation Services and Windows Azure Websites
Rainer Stropek
TFS & software architects gmbh
Email rainer@software-architects.at
WAWS Web http://www.timecockpit.com
Twitter @rstropek
Continuous Integration In The Cloud
Saves the day.
2. Agenda
Source: http://www.flickr.com/photos/riggzy Source: http://www.flickr.com/photos/seeminglee/
/3363502084 4556156477
Common Creative License Common Creative License
Azure Web Team Continuous Resources
Sites Foundatio Integration
n Services
3. • Source of the Windows Azure Websites Slides:
Windows Azure Platform Training Kit
17. Agenda
Source: http://www.flickr.com/photos/riggzy Source: http://www.flickr.com/photos/seeminglee/
/3363502084 4556156477
Common Creative License Common Creative License
Azure Web Team Continuous Resources
Sites Foundatio Integration
n Services
18. Team Foundation Services
TFS in the cloud
Multi-tenant infrastructure with TFS running on the Azure technology platform
Broad functional reach with few limitations
Agile planning tools
Version control
Work item tracking
Build
Free for small team
Use TFS Online as part of your MSDN subscription
Free for small teams with <= 5 members
Unlimited number of projects
19. Team Foundation Services
Build process is still in preview
Currently no cap on build processes
Limitations will apply (e.g. for free subscriptions) at RTM
Currently not further pricing information available
Limitations
No way to customize the process template
No integration with e.g. SharePoint, Project Server, etc.
LiveID is the only authentication mechanism
Reporting is very limited
http://tfs.visualstudio.com
20.
21. Agenda
Source: http://www.flickr.com/photos/riggzy Source: http://www.flickr.com/photos/seeminglee/
/3363502084 4556156477
Common Creative License Common Creative License
Azure Web Team Continuous Resources
Sites Foundatio Integration
n Services
22. Continuous Integration
Connect Web Site project in TFS with a WAWS
Also works for a Cloud Service project connected to a WACS
Trigger a build on every check-in
You can customize the build process
You cannot install any software on the build servers
Deploy the Web Site project to WAWS after
successful build
(If necessary) Roll back to previous version
23.
24. Agenda
Source: http://www.flickr.com/photos/riggzy Source: http://www.flickr.com/photos/seeminglee/
/3363502084 4556156477
Common Creative License Common Creative License
Azure Web Team Continuous Resources
Sites Foundatio Integration
n Services
25. Resources
TFS Online
http://tfs.visualstudio.com
FAQ: https://tfs.visualstudio.com/en-us/support/faq
https://tfs.visualstudio.com/en-us/learn/build/hosted-build-controller-in-vs/
http://blogs.msdn.com/b/buckh/archive/2011/09/19/how-to-delete-a-team-project-from-tfs-on-azure.aspx
Blog post of Brian Harry regarding RTW of TFS
http://blogs.msdn.com/b/bharry/archive/2012/10/31/team-foundation-service-rtm.aspx
Hands-on lab for continuous integration with
TFS and WAWS/WACS
http://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/
26. Continuous Integration with Team Foundation Services and Windows Azure Websites
Rainer Stropek
software architects gmbh
Email rainer@software-architects.at
Q&A Web http://www.timecockpit.com
Twitter @rstropek
Thank you for coming
Saves the day.
Notes de l'éditeur
Slide Objectives:Explain the differences between traditional self-hosting and the three options of Windows Azure hosting.Notes:In a traditional environment you must manage the full stack. With Windows Azure you can choose a variety of options depending on your needs.
Slide Objectives:Explain how Windows Azure websites are simple, easy, and open.Notes:
Slide Objectives:Explain the three scale choices on Windows Azure Web Sites.Notes:Both free and shared are the same architecture. The only difference is that free has quotas where as with shared you can use and pay for as much resources as you choose. With reserved you isolate your application to your own virtual machines that you can use and pay for whatever resources you choose.
Slide Objectives:Explain how you can start with a small site hosted for free.Notes:
Slide Objectives:Explain how you can scale your site to multiple shared instances.Notes:
Slide Objectives:Explain how you can move to reserved instances for additional scale.Notes:
Slide Objectives:Explain how you can scale up reserved instances to multiple instances as needed.Notes:
Slide Objectives:Explain how you can host multiple sites that you own on a your reserved instances.Notes:
DemoLength: 10 minutesCreate Wordpress Blog in Web GalleryDownload Publish FileOpen in WebMatrixEdit ThemeSave/DeployShow site with changesRun locally Add theme -> Can we find an enterprise theme, team status or something similarDeploy to cloudShow running in cloud
Slide Objectives:Explain that Windows Azure Web Sites supports Classic ASP, ASP.NET, PHP, and Node.js out of the box and that you can also host any custom FastCGI handler.Notes:
Slide Objectives:Explain how developers have a choice in publishing methods to Windows Azure Web Sites and that regardless of which method they choose publishing is fast and easy. You can even publish from a non-Windows machine using FTP or Git.Notes: