This document discusses continuous delivery practices for .NET projects. It covers using Git for version control, protecting branches, conducting code reviews, running static analysis and unit tests, and deploying using tools like Octopus Deploy. Challenges of using Visual Studio Team Services are also mentioned. The recommended setup combines GitHub, SonarQube, Fake, xUnit, TeamCity and Octopus.

1. @skalinets 1
Continuous Delivery
Adventures in .NET
Serhiy Kalinets
Technical Architect in Steer73
@skalinets
kalinets@gmail.com

2. @skalinets 2
About Me
16 years in the business
In .NET since 2005
Love to code
Technical Architect @ Steer73

3. @skalinets 3

4. @skalinets 4
Why Continuous Delivery?

5. @skalinets 5
Why .NET?

6. @skalinets 6
.NET developers are
isolated from
others

7. @skalinets 7
Microsoft’s
way of doing
things

8. @skalinets 8
“Not invented here” syndrome
Microsoft
rn
GUI servers, RDP
Massive IDE
F5 Run, F9 Breakpoint (VS)
Project files on the right
Rest of the world
n
SSH, console
Code editor (vim, sublime)
F9 Run, F5 Breakpoint (Delphi)
Project files on the left

9. @skalinets 9
From Jenkins webpage 

10. @skalinets 10
CD Flow
Create PR
Run Static Test Analysis, Unit Tests
Code Review
Merge into dev branch
Prepare deployment artifact, version it
Deploy to dev
Run acceptance tests, approve build
Promote to next environment (QA, Stage,
Prod)

11. @skalinets 11
Version Control
public string GetMostSuitableVersionControl(
int teamSize,
bool teamIsDistributed,
ApplicationType applicationType)
{
return "git";
}

12. @skalinets 12
git + UI
Github
Gitlab
Bitbucket
VSTS

13. @skalinets 13
Protected Branches
Master / develop / release
Cannot be pushed to w/o Pull Request approved
Pull request approval checks
# of likes / approvals
Passing build
All comments are addressed

14. @skalinets 14
Code Review

15. @skalinets 15
Expected Code Review Flow
Pull request is created
Reviewers are invited
Reviewers put their comments
Author resolves comments
Pull request gets merged to dev branch

16. @skalinets 16
Code Review Problems
“Need to fix” status
Build status reporting
Track comment resolution

17. @skalinets 17
Another Core Review Tools
Gerrit from Google
Upsource from JetBrains
Crucible / Fisheye from Atlassian

18. @skalinets 18
Code Analysis
Support for C# out of the box
Roslyn based C# analyzer
Supports R# checks, FxCop, StyleCop etc
SonarLint plugin for Visual Studio

19. @skalinets 19

20. @skalinets 20

21. @skalinets 21
How to build project?

22. @skalinets 22

23. @skalinets 23
Unit tests

24. @skalinets 24
Unit Test Frameworks
MSTest
xUnit
NUnit

25. @skalinets 25
CI Server

26. @skalinets 26
Teamcity
Supports almost any
language / platform
Comprehensive build
setup
Easy setup /
maintenance

27. @skalinets 27

28. @skalinets 28

29. @skalinets 29
Progress

30. @skalinets 30

31. @skalinets 31

32. @skalinets 32
Teamcity
R# Static Code Analysis
Test Run Failure Conditions
Duplicate Finder

33. @skalinets 33
Teamcity
Dependencies
Small resource consumption
Abitlity to run more than one agent on the same
machine
Very user friendly (configuration via files, windows
service management via cmds, and so on)

34. @skalinets 34
Problems
Hung builds cannot always be cancelled
Artifact / snapshot dependencies mess
Hard to switch between admin and project
views

35. @skalinets 35
Jenkins
Lot of plugins
Very flexible
Requires configuration out of the box

36. @skalinets 36

37. @skalinets 37

38. @skalinets 38
Chuck Norris Plugin for Jenkins

39. @skalinets 39
Deployment?

40. @skalinets 40
Build with .NET and for .NET
Deploy anything anywhere
Nuget based deployment -> versioning
Has REST API
Octopus Deploy

41. @skalinets 41

42. @skalinets 42

43. @skalinets 43
Environments
DEV / QA / Stage / Prod etc.
Contain Targets

44. @skalinets 44
Deployment Targets
Tentacles (listening / polling)
Azure Web App
Offline Package Drop (xcopy style)

45. @skalinets 45
Versioning with Gitversion
Generates semver compatible versions
Supports git(hub) flow
Supports custom branching strategies
Generates valid Nuget versions
All configuration is stored in the repo

46. @skalinets 46

47. @skalinets 47
VSTS
“All in one” solution from Microsoft
Different parts can be used separately
Free (to some extent)

48. @skalinets 48

49. @skalinets 49
VSTS

50. @skalinets 50
Key features missing / complicated
Needed to setup branch filter for
deployment
“New” UI did not have that option
at all
“Old” UI had that option but ONLY
for VSTS repository

51. @skalinets 51
Key features missing / complicated
Workaround – add custom tag
during build that is equal to
branch name and use that tag
as deployment filter
Now it got fixed (4 years from
the project start)

52. @skalinets 52
Other issues
Queued builds when all agents are idle
Sporadic hangs of agents
Random deployment errors
Test result reporting
UX issues

53. @skalinets 53

54. @skalinets 54

55. @skalinets 55

56. @skalinets 56
My Choice
Github for code / reviews
SonarQube for code analysis
Fake for build
xUnit for unit / integration tests
Teacity for CI
Octopus for deployment

57. @skalinets 57
Thanks!
@skalinets
kalinets@gmail.com
skalinets.github.io