Cazando Bugs con Integración Continua

C.I. Introductory talk.

Related Links:
https://about.gitlab.com/gitlab-ci/
https://jenkins-ci.org
https://travis-ci.org
https://circleci.com
https://en.wikipedia.org/wiki/Continuous_integration
http://doc.gitlab.com/ce/ci/

http://gitlab.com/cabargas/ruby-getting-started/
http://gitlab.com/cabargas/ruby-getting-started/builds

Transcript

1. BUG HUNTING WITH C.I. MEETUP MARZO 2016 - PROIN CHILE
2. FELIPE CABARGAS M. Service Engineer @ GitLab @juanpintoduran @f cabargas.com gitlab.com/cabargas
3. ALWAYS CODE AS IF THE GUY WHO ENDS UP MAINTAINING YOUR CODE WILL BE A VIOLENT PSYCHOPATH WHO KNOWS WHERE YOU LIVE. Martin Golding CATCH ‘EM ALL WITH C.I.
4. THE ONLY THING MORE EXPENSIVE THAN WRITING SOFTWARE IS WRITING BAD SOFTWARE. Alan Cooper CATCH ‘EM ALL WITH C.I.
5. WHAT IS C.I. ?
7. CONTINUOUS INTEGRATION IS A SOFTWARE DEVELOPMENT PRACTICE WHERE MEMBERS OF A TEAM INTEGRATE THEIR WORK FREQUENTLY, USUALLY EACH PERSON INTEGRATES AT LEAST DAILY - LEADING TO MULTIPLE INTEGRATIONS PER DAY. EACH INTEGRATION IS VERIFIED BY AN AUTOMATED BUILD (INCLUDING TEST) TO DETECT INTEGRATION ERRORS AS QUICKLY AS POSSIBLE
8. http://filecatalyst.com/wp-content/uploads/2014/12/Continuous-Integration-Diagram.png
9. TEST + DEPLOY = INTEGRATION
10. C.I. != T.D.D.
11. C.I. + T.D.D.
12. AVAILABLE C.I. SOLUTIONS
13. GitLab CI
14. C.I. IRL
19. EXAMPLE TIME !
20. THANKS ! Felipe Cabargas M. @juanpintoduran www.cabargas.com Useful resources and links will be provided with this deck @ decks.cabargas.com