Code fast & Break things with Jenkins & Continuous Integration
•
2 likes•8,878 views
Code fast & Break things with Jenkins & Continuous Integration
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Code fast & Break things with Jenkins & Continuous Integration
Similar to Code fast & Break things with Jenkins & Continuous Integration (20)
Recently uploaded
Recently uploaded (20)
Code fast & Break things with Jenkins & Continuous Integration
- 1. Code Fast & Break things With Jenkins & Continuous Integration
- 8. Deployment Pipeline Git Lib Repo 1. Clean 2. Checkout 3. Download libs 4. Compile 5. Package 6. Setup DB 7. Run Tests 8. Deploy Local Web Server Local DB Server
- 9. $ compile *.* $ zip myapp.zip $ scp_upload myapp.zip Step 1: Automate Build
- 10. Step 2: Automate Tests create_user(username, password) user = login(username, password) assert user != null
- 12. 1. Before demo/release 2. When we have time 3. Every week 4. Every day 5. Other When should we run tests? 1. Before demo/release 2. When we have time 3. Every week 4. Every day 5. Other: every time you commit
- 13. Step 3: CI Server Git Lib Repo 1. Clean 2. Checkout 3. Download libs 4. Compile 5. Package 6. Setup DB 7. Run Tests 8. Deploy Local Web Server Local DB Server
- 14. 3.Email report CI Server Build, run, test 1. Clean 2. Checkout 3. Download libs 4. Compile 5. Package 6. Push 7. Setup DB 8. Run Tests 2.Commit trigger Git 1.CommitStep 3: CI Server
- 15. Jenkins Demo!
- 16. $ sudo apt-get install jenkins $ sudo /etc/init.d/jenkins start
- 17. TESTRUNBUILD
- 20. Hervé Vũ Roussel hroussel@gmail.com herveroussel.com slideshare.com/hroussel Thank you! Join me!
- 21. Source code on GitHub Setup CI and demo on YouTube “Online CI providers are the new black”, JoliCode, Feb 2012 Interactive slides on Google Drive Additional resources
Editor's Notes
- Who is doing agile? Who is heard of CI? Who writes automated tests? Who likes testing? Who thinks testing is useless? >> Candy
- 10 years of tech in US Proudest achievement Amazing team Beautiful product Customers loved us
- Customers first Include customers in product conversation >> Quick feedback loop Release implies quality Who said this? >> Candy
- Quick customer feedback Speed VS Quality
- Greatest joy, hired first dev Very smart, very fast BUT didn’t like to test
- Release once every 2 weeks Release @ 2AM Tired Start build process Push to cloud Excited (new cool features delivered to customer) Ooops page @ 2:30AM 1- Fix bug (sleep @ 4-5AM?) 2- Rollback release (delayed release on promise) “You need to test your code!!!!”
- Diner with Peter “This is your fault” I pay him “You lack process, lack definition of quality”
- Brainstorm: what are *my* steps to release? List all steps on whiteboard
- The steps were then scripted Faster, more consistent builds
- I defined quality Too many tests - Core features (login, etc.) - New features (TDD) - Fixes (create ticket with failing test) Goal is to get to 100% coverage
- Testing 1 day before release (every 2 week) Problems: a) Found last minute bugs b) Needle in haystack (hardest part to fixing a bug) => Waiting 2 weeks for testing is too long => Who wants to test after every commit
- Everytime you make a change -> opportunity to break code Write new features -> break old features (login) Who wants to write tests every time?
- Outsource your build, run and test Instant feedback Rob didn’t like testing and CI CI makes it fun to try new things
- What’s the app? Local tests with Firefox Why Jenkins? NOOOO > Limitations of cloud providers: "What’s really missing on all those services is quality tools. When setting up a Jenkins internally, you can add CodeSniffer, PHPMD, JSLint"
- You have to setup another developer workstation Plan: Setup Jenkins job Write bug Email notification
- CI is easy to setup Step2: Goal: 100% test coverage Keep up with: 100% passing tests Take it step by step
- Who said this? >> Candy