from continuous integration to continuous delivery with teamcity

XP Days Ukraine 2016—

November 11, 2016Kiev

From Continuous Integration to Continuous Deliverywith TeamCity—

Sergey PakTeamCity DeveloperJetbrains

About myself—

• Delivering code since 2003

• Improving TeamCity since 2013

• Primary focus - cloud integration

From CI to CD with TC About myself

@JetBrains. All rights reserved

[email protected]

mailto:[email protected]

What is Continuous Integration—

• Integrate into shared mainline

From CI to CD with TC What is CI


What is Continuous Integration—

• Integrate into shared mainline

• Automated self-testing build

• Test every commit

• Everyone can see the results

From CI to CD with TC What is CI


From CI to CD with TC Before TeamCity


Before TeamCity



CruiseControl—

The main and the only CI tool in 2006



CruiseControl—

Edit configuration



We needed another CI tool

Problems to address initially—

• 5 PM Check-in

• Multiple platforms

• UI to edit configurations

From CI to CD with TC TC 1.0




Remote Run—



Remote Run +Pretested Commit—



Remote Run UI—


• 5 PM Check-in - Remote Run + Pretested commit

• Multiple platforms




Build Agent—



Build Agent—

• Required software:



Build Agent—


• Tools and plugins: from server



Build Agent—



• No maintenance required:



Build Agent—



• No maintenance required:• Auto-upgrade



Build Agent—



• No maintenance required:• Auto-upgrade• Can work without server



Build Agent—



• No maintenance required:• Auto-upgrade• Can work without server• Self-cleanup



Build Agent—

Available out of the box:




• 5 PM Check-in

• Multiple platforms - Build agent




TeamCity UI—

2006



TeamCity UI—

2016




• 5 PM Check-in - Remote run + Pretested commit

• Multiple platforms - Build agent




Other problems—



Multiple repos / long checkout Get revisions first

Reuse settings Templates

No responsibility Investigations

Parallel execution Build chains (Snapshot dependencies)

Other problems—



Multiple repos / long checkout Get revisions first

Reuse settings Templates

No responsibility Investigations

Parallel execution Snapshot dependencies(Build chain)

From CI to CD with TC Snapshot dependencies


Snapshot Dependencies

Snapshot dependencies—

• Source-level dependency

• Snapshot = set of VCS revisions




Build chains:

• Chain 1: GDCA• Chain 2: GDHEFB




Trigger one build




Optimize




Results in one place:

• dependencies




Results in one place:

• tests



From CI to CD with TC Feature branches


Feature branches

Feature branches—

SVN vs GitMarketshare



Feature branches—

• Same build configuration



Feature branches—


• Branch - build/test attribute



Feature branches—


• Branch - build/test attribute

• Different settings per branch



Feature branchesUI—

Overview




History




Build chains




Test history



DVСS Support—

• Mirrors on agents

• Sparse checkout

• Subrepo/submodule support

• Auto-merge



From CI to CD with TC Cloud integration


Cloud integration

Why Cloud?—



Why Cloud?—



• Easier maintenance

Why Cloud?—




Why Cloud?—



• Scalability

Why Cloud?—


• Scalability• EC2 spot instances supported



Cloud Integration—



Dogfooding vs External Feedback—

From CI to CD with TC Dogfooding


Features from Jetbrainers—

• Feature branches

• Fix revisions before build

• Snapshot dependencies

• Remote run



Features from customers—

• Multiple build steps

• Project hierarchy

• Per-project permissions (+roles)

• Cloud integration





Want your feature?Let us know!

https://youtrack.jetbrains.com

https://youtrack.jetbrains.com/

From CI to CD with TC Continuous Deployment


Continuous Deploymentof

TeamCity with TeamCity

Why CD?—



Why CD?—

• Less changes per update



Why CD?—



67

Why CD?—

• Less changes per update

• Early feedback



TeamCity CD—

TeamCity = Service + Product



TeamCity CD—

Numbers:

• 17,000 tests

• Test coverage 65%

• 46 configurations



TeamCity CD—

Instance size:

• 320 agents (220 - vmware)

• 25,000 builds per day

• 600 users

• 4000 build configurations in 700 projects

• 10TB artifacts



TeamCity CD—

Instance size:

• 10 CPU Cores

• -Xmx10G



TeamCity CD—

• Unit tests

• Integration tests

• Acceptance tests

• Code review



TeamCity CD—

• Unit tests

• Integration tests

• Acceptance tests

• Code review



= Trusted package

TeamCity CDTrusted package—



TeamCity CDDeployment—



Conclusion—

• Use TeamCity - it’s free to start

• Get in touch with us:• https://youtrack.jetbrains.com• [email protected]• [email protected]

• Happy building!



https://youtrack.jetbrains.com/



Thank you for your attention—

jetbrains.com

from continuous integration to continuous delivery with teamcity

Software