Overview
-
Learn how to set up a continuous integration/continuous delivery workflow with TeamCity 2017 to build, test, and deploy code as a team.
Syllabus
-
Introduction
- Welcome
- TeamCity 2017 CI/CD architecture
- Install TeamCity 2017 server on Windows Server 2016
- Types of build agents in TeamCity 2017
- Install build agents on an existing Windows Server
- TeamCity 2017 cloud build agents, part 1
- TeamCity 2017 cloud build agents, part 2
- TeamCity 2017 cloud build agents, part 3
- Connect to a Version Control System (VCS)
- VCS root connections and open authentication
- Ways of organizing projects in TeamCity
- Create your first TeamCity project
- Tools, build steps, parameters, and templates
- Build and package ASP.NET MVC projects
- Run unit tests (NUnit) with TeamCity
- Perform code quality inspections
- Monitor branches and auto-merge feature branches
- Monitor and verify pull requests
- Transform Web.config files using MS Build
- Transform Web.config files using PowerShell
- Deployment architecture and strategy
- Checkout rules and install plugins
- IAM roles, SNS topics, and CodeDeploy agent
- Steps of deploying with AWS CodeDeploy and TeamCity
- Create CodeDeploy applications
- Create appspec.yml and hook scripts
- Deploy artifact with TeamCity Artifact Dependencies and AWS CodeDeploy
- VCS triggers and CI/CD with snapshot dependencies
- Scheduled triggers
- Failure conditions
- Users, groups, and roles
- User activity audit
- Manage and subscribe to notifications
