Post on 22-Jan-2018
Ángel García
@angel_g_santos
Senior Developer
agarcia@pasiona.com
huorswords@gmail.com
@
fotosilueta
Continuous Integration
¿Qué es?
Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
https://www.thoughtworks.com/es/continuous-integration
Continuous Delivery
¿Qué es?
Through reliable, low-risk releases, Continuous Delivery makes it possible to continuously adapt software in line with user feedback, shifts in the market and changes to business strategy. Test, support, development and operations work together as one delivery team to automate and streamline the build, test and release process
https://www.thoughtworks.com/continuous-delivery
¿Por qué?• Visual Studio Team Services
• Integración out-of-the-box con Git• Integración out-of-the-box con Azure• SCV, Build, Release, Deploy management
• Azure• WebApps• Máquinas virtuales• Bases de datos• Infraestructura• Storage• …
• Y porque es de Microsoft
¿Por qué?
Continuous Integration
Estrategias CI - Build
• Planificada (… y nightlies)• Inmediata• Gated Commit / Check in• Manual
• La estrategia de branching determinaqué ramas deben ser compiladasmediante una build automática.
• En GitFlow, tiene sentido tener al menos dos entornos automatizados: master y develop
Estrategia de branching - GitFlow
Continuous Integration