devops - más allá del botón derecho > publicar | 4sessions feb17
TRANSCRIPT
DevOpsMás allá de “Botón derecho > Publicar”
#FourSessions
Ángel García
DevOps
DevOps
DevOps
DevOps
Etapas
DevOps
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
I choose you!
• Git• GitFlow
¿Por qué?
¿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é?
Visual Studio Dev Essentials
https://www.visualstudio.com/es/dev-essentials/
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
DEMO
Continuous Delivery
Deploy
• WebApp• Nuget• Store• …
Continuous Delivery
Estrategias CD - Release
• Planificada (… y nightlies)• Inmediata• Manual
DEMO
DevOps
Code Build Test Release Deploy
Resumen
DevOps
Code Build Test Release Deploy
Resumen
DevOps
Code Build Test Release Deploy
Resumen
GRACIAS