Continuous integration meetup
•Download as PPT, PDF•
0 likes•899 views
This document discusses the benefits of continuous integration using Jenkins. It explains that continuous integration helps eliminate bugs by running automated tests frequently to catch errors early. This allows teams to work more efficiently by preventing the need to revisit features after integration. Jenkins is highlighted as a tool that can run tests automatically, notify teams of failures, and help set up new machines for continuous integration workflows. Setting up scripts in source control is recommended so the Jenkins process can be repeated reliably.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Continuous integration meetup
Similar to Continuous integration meetup (20)
Recently uploaded
Recently uploaded (20)
Continuous integration meetup
- 1. Palomino Labs, Inc. palominolabs.com Continuous Integration, Agile, and Jenkins, Oh My!
- 4. Why Continuous Integration? • Desire be lean & agile • Google does it • Small startups do it • Everyone talks about it • VP read a blog post
- 6. Eliminate Waste • Bugs are bad • Tests prevent bugs • Tests find bugs early
- 7. One Piece Flow • Eliminate need to revisit features Source: 1991, Gerald Weinberg, Quality Software Management: Systems Thinking
- 8. One Piece Flow • Eliminate need to revisit features • Faster shipping = more money
- 9. One Piece Flow • Eliminate need to revisit features • Faster shipping = more money • More money = happiness
- 10. This Is Where Jenkins Comes In • Tests runs must be automatic • Stop the line • No false positives • Failures must be visible
- 11. Notify on Failure • Email team on failure
- 12. Setting Up a New Machine • AWS? Use EBS • Allows snapshotting & embiggening • Ubuntu wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add - sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list' sudo apt-get update sudo apt-get install jenkins • RHEL/CentOS/Amazon Linux sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo sudo rpm --import http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key yum install jenkins
- 13. A Good Jenkins setup • Do all of your work in a script • Check script into source control • Rejoice when a mistake is made
- 14. Rails Run Script
- 15. Run All Of Your Tests
- 16. Tests Dependent Upon Other Systems Details: http://blog.palominolabs.com/2013/05/06/ruby-testing-and-external-dependencies/
- 17. Bonuses • HIPAA compliance • Performance tests over time
- 18. Palomino Labs, Inc. palominolabs.com Drew Stephens drew@palominolabs.com @dinomite
Editor's Notes
- Principal at Palomino Labs; software development consultancy Desktop webapps, native mobile apps, low level systems programming, and big data Also process consulting, focusing on making teams more efficient
- GORUCK challenge is about building an efficient team
- If you don’t understand why you’re doing something, you’re going to have a bad time
- The core of what we’re trying to do with CI & lean principles is efficiency
- We’re trying to eliminate waste and the prime way to do that is reducing bugs Finding & fixing bug is a waste of time; the best thing to do is eliminate them Writing testable code and the tests for it, be they unit or more comprehensive, helps prevent bugs in the first place Tests find regressions early
- Be it bugs or simultaneous feature development, context switching is costly. By eliminating bugs you decrease the need to revisit features.
- Be it bugs or simultaneous feature development, context switching is costly. By eliminating bugs you decrease the need to revisit features.
- Be it bugs or simultaneous feature development, context switching is costly. By eliminating bugs you decrease the need to revisit features.
- Must have automatic test runs Stop the line reduces cost of context switching—find problems sooner
- Jenkins has this box. Many are tempted to do things in it. They cry when the something goes wrong and they lose their build script. Relate to database triggers—hidden code that is ungreppable
- Even though DB setup ought to only happen once, you’ll be happier (and prevent potential failures) if you check it every time.
- Interaction between sdms-cucumber & s3cp Mocks are OK for unit tests, but not integration—systems can change without the mocks being updated Selenium tests take a while—use Sauce or VMs
- HIPAA requires proof of tests run against code on production We’re keeping data in OpenTSDB, producing graphs for each Jenkins run