Continuous Integration

Transcription

1 How painful was your last release? Continuous Integration Marcin Kawalerowicz CEO CODEFUSION Sp. z o. o. CODEFUSION Sp. z o.o. ul. Powstańców Śląskich 25/ Opole, Poland [email protected]

2 After the session you will know what continuous integration (CI) is and why it s worth to use it. You will be able to build small but complete CI process. You will know what to do if the build fails.

3 It is an automated process that builds (link, compile, tests, analyzes, deploy, ) the software after each change in source code, to ensure its health (weather it functions correctly, follows best practices, is deployable, ) provides immediate feedback especially if it s not well.

4

5

6 To fight the integration hell To detect every drop in source code quality To reduce risk To increase the software development process transparency To increase the quality of software To ensure good practices and rule obedience while coding To develop faster with fewer bugs To easily create deployable software Side effect: ensure smooth start for new developers

7 Command line mini CI

8 Prepare -> Check-> Compile -> Test/deploy-> Problem? -> Wait->

9 Source code control Build automation CI server Feedback mechanism Unit testing framework Code analysis

10 Use version control no excuses!!! Vanilla CI server Everyting in repo Including: libs, tools, scripts Excluding: SDKs, Frameworks Clean project strucure

11 Keep everything you need in repository Organize files in groups

12 Script as text Under version control in the same repo Path agnostic Of course DRY don t repeat yourself (use variables, externalize configuration, use system variables, parametrize)

13 Is it still a duel? NAnt MSBuild OpenSource Cross-platform Good if you already know Ant Build-in to.net Framework Integrated with Visual Studio Actively developed Build in features

14 Transition from directed graph to taks loop

15 How much money do you have to spend? Do you want to pay the angle bracket tax (XML) configuration overhead? Is it supporting the tools that you need? How good is the documentation and support? Does it do what you want it to do? Does it do more than you need not just now but into the future? Is it easy to use? Is it cool and hip?

16 Aspekt TFS Hudson/Jenkins TeamCity CC.NET Koszt Konfiguracja Narzędzia Dokumentacja Funkcje Dodatki Łatwość użycia Cool

17 Bamboo Anthil Cruise Go CI is about what people do, not about what tools they use

18

19 Manual / Forced Continuous Integration Poll vs. Push (using hooks) Rolling build (every x check-ins or x seconds) Scheduled (Daily / Nightly / Weekly / ) Triggered by another build

20

21

22 make your unit tests fast and unambiguous have your unit tests as few dependencies as possible let errors drive your unit tests mock external interfaces

23 Tools: Selenium (Web) White Framework (Win, Silverlight) Fitnesse (Acceptance) Visual Studio UI Automation (Web, Win)

24 Not everything considerable for CI Other System Functional Integration CI Unit

25 perform the quick tests at the beginning break the build after first failing test Unit tests Integration tests System tests Other tests

26

27 Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.

28 FxCop / VS Code Analysis IL code analyze FxCop and Visual Studio Code Analysis Extending FxCop CI integration

29 StyleCop C# code analyze Extending StyleCop CI integration

30

31 give information about any decrease of your code quality be quick be able to provide information in diverse art point to the specific place that caused this deterioration be accessible to any team member, anytime

32 Tray notifiers Alternative notifiers Sms Instant messaging Gadgets

33

34 no one pulls anything from source control. The source is broken so no one should be interested in broken code someone should jump right in to fix the problem, preferably the person that caused it, but volunteers are welcome all the commits to the repository are withheld until the build is fixed. If you push good code into a spoiled repository your code might get the smell too

35 Why not? Database as script (in repo) Automatic DB creation Automatic DB migration and seeding Parameter externalization Integration with every change

36 Liquibase Dbdeploy MIGRATEdb Dbmaintain AutoPatch

37 Generating documentation (Sandcastle) XML- Dokumentationskommentare in Quellcode Kompiler XML Dokumentation Sandastle CHM/HTML-Dokumentation Deployment (Wix, MSDeploy) UI automation

38

39 Getting x last build to success Sunny / Clouded / Storming in Jenkins

40 When: Code base / test no. increases -> build time increases Teams growth No. of projects grows Then Create targeted builds (dev build, qa build) Write fast unit tests Smaller teams with local integration servers Modularize the code base Scale hardware Add more build agents Parallelize

41 Quick integration = more frequent integration = high quality source code It should take no more then 5-10 minutes. Scaling Continuous Integration, R. Owen Rogers, Lecture Notes in Computer Science, 2004, Volume 3092, Extreme Programming and Agile Processes in Software Engineering, Pages 68-76

42 Software Developer + IT Professional = Build Master DevOps

43 Continuous delivery Deployment pipeline Commit stage Acceptance stage Self serviced deployments Push button releases

44 CI

45 Marcin Kawalerowicz CEO CODEFUSION Sp. z o. o. [email protected] Blog: LinkedIn: Book: CODEFUSION Sp. z o.o. ul. Powstańców Śląskich 25/ Opole [email protected]