÷ÈÓ°Ö±²¥

Creemos que las compa?¨ªas deben adoptar pr¨¢cticas de despliegue continuo siempre que sea posible. El despliegue continuo es la pr¨¢ctica de desplegar autom¨¢ticamente a producci¨®n cada cambio que pasa las pruebas automatizadas. Esta pr¨¢ctica es un factor clave para lograr ciclos r¨¢pidos de retroalimentaci¨®n y permite a las organizaciones entregar valor a los clientes de manera m¨¢s r¨¢pida y eficiente. El despliegue continuo difiere de la entrega continua en que esta ¨²ltima s¨®lo requiere que el c¨®digo pueda ser desplegado en cualquier momento; no requiere que cada cambio realmente ±ð²õ³Ù¨¦ desplegado en producci¨®n. En el pasado hab¨ªamos dudado si mover el despliegue continuo hacia el anillo de Adopci¨®n, ya que es una pr¨¢ctica que requiere un alto nivel de madurez en otras ¨¢reas de la entrega de software y por lo tanto no es apropiada para todos los equipos. Sin embargo, el reciente libro de la Thoughtworker Valentina Servile proporciona una gu¨ªa exhaustiva para implementar esta pr¨¢ctica en una organizaci¨®n. Ofrece un roadmap para que las organizaciones la sigan y as¨ª logren alcanzar el nivel de madurez requerido para adoptar pr¨¢cticas de despliegue continuo.

If you are wondering ¡°What comes after agile?,¡± you should look towards continuous delivery. While your development processes may be fully optimized, it still might take your organization weeks or months to get a single change into production. Continuous delivery focuses on maximizing automation including infrastructure as code, environment management and deployment automation to ensure your system is always ready for production. It is about tightening your feedback loops and not putting off anything until the end. Continuous delivery is not the same as continuous deployment, which means deploying every change to production. Continuous delivery is not a cowboy show. It puts you in charge of your production environment. The business can pick and choose what and when to deploy. If you think you¡¯ve nailed agile development, but aren¡¯t considering how to achieve continuous delivery, you really haven¡¯t even started.

The past 2 years or more has seen a proliferation of continuous integration tools and platforms leading to substantial innovation in the build and release space. Distribution of builds is one such innovation and yet another is the way in which builds are now structured to make greater use of automation in various stages of the build. Build pipelines help to provide greater insight into the quality of each build and the environments to which they have been deployed. A natural expansion of the build pipeline meme is the adoption of continuous deployment techniques, where the intention is to extend the build pipeline into the production environment. This relies on automated deployment techniques and authorization mechanisms built into the continuous integration toolset. One of the key benefits is the ability to move new functionality into production rapidly and reliably.