Enable javascript in your browser for better experience. Need to know to enable it?

÷ÈÓ°Ö±²¥

Pipelines para infraestructura como c¨®digo

La informaci¨®n en esta p¨¢gina no se encuentra completamente disponible en tu idioma de preferencia. Muy pronto esperamos tenerla completamente disponible en otros idiomas. Para obtener informaci¨®n en tu idioma de preferencia, por favor descarga el PDF ²¹±ç³Ü¨ª.
?ltima actualizaci¨®n : Nov 20, 2019
NO EN LA EDICI?N ACTUAL
Este blip no est¨¢ en la edici¨®n actual del Radar. Si ha aparecido en una de las ¨²ltimas ediciones, es probable que siga siendo relevante. Si es m¨¢s antiguo, es posible que ya no sea relevante y que nuestra valoraci¨®n sea diferente hoy en d¨ªa. Desgraciadamente, no tenemos el ancho de banda necesario para revisar continuamente los anuncios de ediciones anteriores del Radar. Entender m¨¢s
Nov 2019
Adoptar ?

El uso de pipelines de entrega continua para orquestar el proceso de entrega de software se ha vuelto un concepto popular. Herramientas de CI/CD pueden ser usadas para testear configuraciones de servidores (ej: Packer), aprovisionamiento de ambientes (ej: Terraform, CloudFormation) y la integraci¨®n de ambientes. El uso de pipelines para infraestructura como c¨®digo permite encontrar errores antes de que los cambios sean aplicados en los entornos operacionales - incluyendo entornos utilizados para desarrollo y test. Tambi¨¦n ofrecen una manera de asegurar que las herramientas de infraestructuras se est¨¢n ejecutando consistentemente, utilizando agentes CI/CD en vez de workstations individuales. Nuestros equipos han tenido buenos resultados utilizando esta t¨¦cnica en sus proyectos.

May 2018
Probar ?

The use of continuous delivery pipelines to orchestrate the release process for software has become a mainstream concept. However, automatically testing changes to infrastructure code isn¡¯t as widely understood. Continuous integration (CI) and continuous delivery (CD) tools can be used to test server configuration (e.g., Chef cookbooks, Puppet modules, Ansible playbooks), server image building (e.g., Packer), environment provisioning (e.g., Terraform, CloudFormation) and integration of environments. The use of pipelines for infrastructure as code enables errors to be found before changes are applied to operational environments ¡ª including environments used for development and testing. They also offer a way to ensure that infrastructure tooling is run consistently, from CI/CD agents, as opposed to being run from individual workstations. Some challenges remain, however, such as the longer feedback loops associated with standing up containers and virtual machines. Still, we've found this to be a valuable technique.

Nov 2017
Probar ?

The use of continuous delivery pipelines to orchestrate the release process for software has become a mainstream concept. However, automatically testing changes to infrastructure code isn¡¯t as widely understood. Continuous integration (CI) and continuous delivery (CD) tools can be used to test server configuration (e.g., Chef cookbooks, Puppet modules, Ansible playbooks), server image building (e.g., Packer), environment provisioning (e.g., Terraform, CloudFormation) and integration of environments. The use of pipelines for infrastructure as code enables errors to be found before changes are applied to operational environments ¡ª including environments used for development and testing. They also offer a way to ensure that infrastructure tooling is run consistently, from CI/CD agents, as opposed to being run from individual workstations. Some challenges remain, however, such as the longer feedback loops associated with standing up containers and virtual machines. Still, we've found this to be a valuable technique.

Publicado : Nov 30, 2017

Suscr¨ªbete al bolet¨ªn informativo de Technology Radar

?

?

?

?

Suscr¨ªbete ahora

Visita nuestro archivo para leer los vol¨²menes anteriores