continuous integration
TRANSCRIPT
Jéferson Machado So#ware Design
Social network informa0on
http://twitter.com/jefersonm http://facebook.com/jefe.machado
https://github.com/jefersonm/ http://slideshare.net/jefersonm
CONTINUOUS INTEGRATION
BUILDING A FEATURE WITH CONTINUOUS INTEGRATION
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 WHAT'S HAPPENING
MAINTAIN A SINGLE SOURCE REPOSITORY.
AUTOMATE THE BUILD
RAKE
MAKE YOUR BUILD SELF-TESTING
EVERYONE COMMITS TO THE MAINLINE EVERY DAY
SPLIT YOUR WORK INTO TASKS
COMMIT FREQUENTLY (HOURS)
EVERY COMMIT SHOULD BUILD THE MAINLINE ON AN INTEGRATION
MACHINE
TWO OPTIONS: 1- MANUALLY 2- AUTOMATICALLY
KEEP THE BUILD FAST
TWO STAGE BUILDS: 1- UNIT TESTS 2- INTEGRATION TESTS
TEST IN A CLONE OF THE PRODUCTION ENVIRONMENT
TEST ENV - OPERATIONAL SYSTEM - DATABASE SOFTWARE - LIBRARIES - IP ADDRESS - PORTS
PROD ENV - OPERATIONAL SYSTEM - DATABASE SOFTWARE - LIBRARIES - IP ADDRESS - PORTS
EVERYONE CAN SEE WHAT'S HAPPENING
BENEFITS OF CONTINUOUS INTEGRATION
Jéferson Machado So#ware Design
Social network informa0on
http://twitter.com/jefersonm http://facebook.com/jefe.machado
https://github.com/jefersonm/ http://slideshare.net/jefersonm
If you break the build I’ll charge you!!!
Thank you.. Bééé!!