Created 2 years ago
What's New for Build Automation in Team Foundation Server and Visual Studio Online
Email this Mix
Slide 1 - Chris Patterson
- Senior Program Manager
- What's New for Build Automation in Team Foundation Server and Visual Studio Online
- //build/ content is being presented by Microsoft Office Mix The video for this session will be available shortly
Slide 2 - Quick Intro
- Agenda slide
Slide 3 - Quick Intro
Slide 4 - Why?
Slide 5 - How do I customize by build definition to run a script after I build my solution?
Slide 6 - Do you have an integration with <Insert Tool/Service Here>
Slide 7 - Can I build my iOS and Android apps with TFS?
Slide 8 - What about my enterprise Java app?
Slide 9 - I have to have the latest version of VS just to edit my build definition?
Slide 10 - Where do I find my build log?
Slide 11 - Opens XAML template for the first timeYou’re kidding right?
Slide 12 - Principles
- Do not create a new build/automation DSL
- Our solution must support non-windows platforms natively
- Intentional Extensibility (build a community)
- Don’t hide the log from me
Slide 13 - Show me the goods
- File new build my solution
- Continuous delivery awesome
- Fruity goodness
- I have the next great app idea
Slide 14 - Nitty gritty details
Slide 15 - No New Build DSL
- There are more than enough to go around
- Don’t me learn yours just to run mine
Slide 16 - Native cross platform
- Node.js based xplat agent
- OOB support for common xplat technologies
- Open Source
Slide 17 - Extensibility
- Focus on Scripts First
- You shouldn’t need to write a task in most cases
- Zip file uploaded to server and automatically downloaded to the agent
- All OOB tasks will be open source
- Build a community around extensions
- Task implementation
Slide 18 - Don’t hide my log
Slide 19 - SxS with XAML Builds
- Will continue to support 2010 and forward controllers in Dev14
- No more physical controller
- Agent pools defined at the deployment level with collections assigned to use them
- Agents are xcopy deployed and auto updated from server.
Slide 20 - Agent Architecture
- TFS Deployment
- Machine 1
- Machine 2
- Machine 3
- Http Traffic
Slide 21 - Security
- Each build runs in it’s own process
- One build can’t corrupt the process space for the next build
- Pool administration can be delegated
- You don’t need collection or deployment wide permissions to register build resources
- Each build get’s a unique access token that is limited in both scope and time.
- Developer can’t write a unit test to access resources they are not supposed to
Slide 22 - Download the TFS RC and take it for a spin
- New build pools will show up in your account in a couple of weeks
- Call to Action