CONTINUOUS INTEGRATION	                          Social	  network	  informa0on	                          http://twitter.co...
BUILDING A FEATURE WITHCONTINUOUS INTEGRATION 	  
PRACTICES OF CONTINUOUS              INTEGRATION•  MAINTAIN A SINGLE SOURCE REPOSITORY.•  AUTOMATE THE BUILD•  MAKE YOUR B...
MAINTAIN A SINGLE SOURCE       REPOSITORY.
AUTOMATE THE BUILD           RAKE	  
MAKE YOUR BUILD SELF-TESTING
EVERYONE COMMITS TO THE            MAINLINE EVERY DAY                       COMMIT FREQUENTLY                       (HOURS...
EVERY COMMIT SHOULD BUILD THE  MAINLINE ON AN INTEGRATION           MACHINE       TWO OPTIONS:       1- MANUALLY       2- ...
KEEP THE BUILD FAST         TWO STAGE BUILDS:         1- UNIT TESTS         2- INTEGRATION TESTS	  
TEST IN A CLONE OF THE      PRODUCTION ENVIRONMENTTEST ENV                  PROD ENV-    OPERATIONAL SYSTEM   -    OPERATI...
EVERYONE CAN SEE WHATS       HAPPENING
BENEFITS OF CONTINUOUS      INTEGRATION	  
If	  you	  break	  the	  build	  I’ll	                                                                         charge	  yo...
Upcoming SlideShare
Loading in …5
×

Continuous integration

195
-1

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
195
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Continuous integration

  1. 1. CONTINUOUS INTEGRATION   Social  network  informa0on   http://twitter.com/jefersonm https://github.com/jefersonm/Jéferson MachadoSo#ware  Design   http://facebook.com/jefe.machado http://slideshare.net/jefersonm
  2. 2. BUILDING A FEATURE WITHCONTINUOUS INTEGRATION  
  3. 3. PRACTICES OF CONTINUOUS INTEGRATION•  MAINTAIN A SINGLE SOURCE REPOSITORY.•  AUTOMATE THE BUILD•  MAKE YOUR BUILD SELF-TESTING•  EVERYONE COMMITS TO THE MAINLINE EVERY DAY•  EVERY COMMIT SHOULD BUILD THE MAINLINE ON AN INTEGRATION MACHINE•  KEEP THE BUILD FAST•  TEST IN A CLONE OF THE PRODUCTION ENVIRONMENT•  EVERYONE CAN SEE WHATS HAPPENING
  4. 4. MAINTAIN A SINGLE SOURCE REPOSITORY.
  5. 5. AUTOMATE THE BUILD RAKE  
  6. 6. MAKE YOUR BUILD SELF-TESTING
  7. 7. EVERYONE COMMITS TO THE MAINLINE EVERY DAY COMMIT FREQUENTLY (HOURS)  SPLIT YOUR WORK INTOTASKS  
  8. 8. EVERY COMMIT SHOULD BUILD THE MAINLINE ON AN INTEGRATION MACHINE TWO OPTIONS: 1- MANUALLY 2- AUTOMATICALLY  
  9. 9. KEEP THE BUILD FAST TWO STAGE BUILDS: 1- UNIT TESTS 2- INTEGRATION TESTS  
  10. 10. TEST IN A CLONE OF THE PRODUCTION ENVIRONMENTTEST ENV PROD ENV-  OPERATIONAL SYSTEM -  OPERATIONAL SYSTEM-  DATABASE SOFTWARE -  DATABASE SOFTWARE-  LIBRARIES -  LIBRARIES-  IP ADDRESS -  IP ADDRESS-  PORTS -  PORTS
  11. 11. EVERYONE CAN SEE WHATS HAPPENING
  12. 12. BENEFITS OF CONTINUOUS INTEGRATION  
  13. 13. If  you  break  the  build  I’ll   charge  you!!!     Thank  you..  Bééé!!   Social  network  informa0on   http://twitter.com/jefersonm https://github.com/jefersonm/Jéferson MachadoSo#ware  Design   http://facebook.com/jefe.machado http://slideshare.net/jefersonm
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×