Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Integration and Continuous Deployment

Continuous Integration and Continuous Deployment

This session focuses specifically on continuous integration builds, automated testing, and continuous delivery/deployment. We will use Visual Studio Team Services with an emphasis on how VSTS integrates with third party and OSS tools, such as Git and Jenkins, which are widely used across development teams practicing DevOps. We will discuss Continuous Integration Strategies, including source control, branching, and code review, pipelines and agents.

Daron Yondem

October 26, 2017

More Decks by Daron Yondem

Other Decks in Programming


  1. The Three pillars of Continuous Integration • Version Control System

    • Git • Subversion • TFVC • Continuous Integration System • Visual Studio Team Services • Jenkins • Team City • Automated Build Process • Team Build • Ant • Nant • Gradle
  2. Centralized vs. Distributed Source Control Systems • Centralized • One

    server somewhere • Feels waterfall • History on the server • Checkout / Checkin (Who has that file checked out?) • Always connected. • Easy to scale to large codebases. • Granular permission control (constant connection remember?)
  3. Centralized vs. Distributed Source Control Systems • Distributed • No

    central authority, every node is a server. • Usually comes with cross platform support. • Automated baked in (Pull Requests, Gate Hooks) • Complete offline support (history data included) • Large code base (long history) hard to manage locally. • Good for highly distributed teams.