1 / 26

Continuous Integration: Best Practices and Tools

Explore the importance of Continuous Integration through best practices, hardware setups, and tools like Jenkins for efficient software development. Learn how to integrate, test, and automate builds seamlessly.

bankston
Télécharger la présentation

Continuous Integration: Best Practices and Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lecture XIII: Continuous Integration CS 4593Cloud-Oriented Big Data and Software Engineering

  2. Continuous Integration • We introduced Continuous Deployment • Continuous Update for the whole software process: Continuous Integration 2

  3. Continuous Integration • Teams integrate their work multiple timesper day. • Each integration is verified by an automated build • Significantly reduces integration problems • Develop cohesive software more rapidly Source: Martin Fowler

  4. Five Principles of Continuous Integration • Environments based on stability • Maintain a code repository • Commit frequently and build every commit • Make the build self-testing

  5. Environments based on stability • Create server environments to model code stability • Promote code to stricter environments as quality improves.

  6. Production Environment Hardware • Application servers • 8 application server • 12 cores, 48 GB RAM • 10 web server • 2 cores, 2 GB RAM • Database servers • 4 web databases • 4 cores, 16 GB, 2 SSD • 1 application database • 12 cores, 48 GB RAM, 15 SSD

  7. Stage Environment Hardware • Application servers • 7 application server • 4 cores, 4 GB RAM • 2 web server • 2 cores, 2 GB RAM • Database servers • 1 web database • 4 cores, 16 GB, 8 SAS • 1 application database • 8 cores, 16 GB RAM, 16 SATA • Continuous Integration Server • 2 cores, 4 GB RAM, 1 SATA

  8. Test Environment Hardware • Each team of 8 developers has a test environment • VM server • 4 cores, 16 GB RAM • Database servers • 4 cores, 24 GB RAM, 8 SATA drives • Continuous Integration Server • 8 cores, 16 GB RAM, 1 SATA drive

  9. Dev Environment Hardware • Application servers • Workstations with 4 cores, 8 GB RAM • One per developer • Database servers • Shared with Test environment

  10. Commit Frequently Build Every Commit • Change your habits • Commit small, functional changes • Unit tests! • Team owns the code, not the individual

  11. The code builds on my box... • Source code repository is the source of record • Build server settles disputes • Only gets code from Repo • Build server the final authority on stability/quality

  12. Build every commit • Why compile frequently? • Agile principles • If it hurts, do it more often. • Many difficult activities can be made much more straightforward by doing them more frequently. • Reduce time between defect introduction and removal • Automate the build • Key to continuous integration

  13. Add testing to build • Individual programmers <50% efficient at finding their own bugs • Multiple quality methods = more defects discovered • Use 3 or more methods for >90% defect removal • Most effective methods • design inspections • code inspections • Testing • Source: http://www.scribd.com/doc/7758538/Capers-Jones-Software-Quality-in-2008

  14. Self Testing Builds • System Tests • End-to-end test • Often take minutes to hours to run • Unit tests • Fast • No database or file system • Focused • Pinpoint problems • Best method for verifying builds

  15. Automated Quality with Continuous Integration • Static code analysis • Looks for common java bugs (Findbugs, PMD) • Check for code compliance (Checkstyle) • Unit test analysis • Measure coverage (Cobertura) • Look for hotspots, areas of low testing and high complexity (SONAR)

  16. Build Server Hardware • Maven and Java = lots of memory • Compile and unit test = lots of CPU • Static analysis = lots and lots of CPU • 8 cores, 16GB RAM, 2 SATA • Ubuntu Linux • 8 parallel builds • KEEP IT FAST

  17. Free Continuous Integration Servers • Cruise Control (ThoughtWorks) • Yucky XML configuration • Commercial version (Cruise) is a rewrite • Continuum (Apache) • Great Maven support • No plugins, ok user interface, and slow builds • Hudson (Oracle) • Self updating and easy to administor • Many useful plugins • Great user interface • Scale out with additional nodes • Best by a wide margin

  18. Jenkins for Continuous Integration • Jenkins – open source continuous integration server • Jenkins (http://jenkins-ci.org/) is • Easy to install • Easy to use • Multi-technology • Multi-platform • Widely used • Extensible • Free

  19. Jenkins for a Developer • Easy to install • Download one file – jenkins.war • Run one command – java –jar jenkins.war • Easy to use • Create a new job – checkout and build a small project • Checkin a change – watch it build • Create a test – watch it build and run • Fix a test – checkin and watch it pass • Multi-technology • Build C, Java, C#, Python, Perl, SQL, etc. • Test with Junit, Nunit, MSTest, etc.

  20. Developer demo goes here… • Create a new job from a Subversion repository • Build that code, see build results • Run its tests, see test results • Make a change and watch it run through the system • Languages • Java • C • Python

  21. More Power – Jenkins Plugins • Jenkins has over 300 plugins • Software configuration management • Builders • Test Frameworks • Virtual Machine Controllers • Notifiers • Static Analyzers

  22. Jenkins Plugins - SCM • Version Control Systems • Accurev • Bazaar • BitKeeper • ClearCase • Darcs • Dimensions • Git • Harvest • MKS Integrity • PVCS • StarTeam • Subversion • Team Foundation Server • Visual SourceSafe

  23. Jenkins Plugins – Build & Test • Build Tools • Ant • Maven • MSBuild • Cmake • Gradle • Grails • Scons • Groovy • Test Frameworks • Junit • Nunit • MSTest • Selenium • Fitnesse

  24. Jenkins Plugins – Analyzers • Static Analysis • Checkstyle • CodeScanner • DRY • Crap4j • Findbugs • PMD • Fortify • Sonar • FXCop • Code Coverage • Emma • Cobertura • Clover • GCC/GCOV

  25. Jenkins Plugins – Other Tools • Notification • Twitter • Campfire • Google Calendar • IM • IRC • Lava Lamp • Sounds • Speak • Authorization • Active Directory • LDAP • Virtual Machines • Amazon EC2 • VMWare • VirtualBox • Xen • Libvirt

  26. Jenkins for Teams Multi-configuration jobs Multi-stage jobs Swarms to dynamically contribute capacity

More Related