O uso de pipelines de entrega cont¨ªnua para orquestrar o processo de release para software se tornou um conceito comum. Ferramentas de CI/CD podem ser usadas para testar a configura??o do servidor (ex.: cookbooks do Chef, m¨®dulos Puppet, playbooks do Ansible), constru??o de imagem do servidor (ex.: Packer), provisionamento de ambiente (ex.: Terraform, CloudFormation) e a integra??o de ambientes. O uso de pipelines para infraestrutura como c¨®digo permite que voc¨º encontre erros antes das mudan?as serem aplicadas em ambientes operacionais ¨C incluindo ambientes usados para desenvolvimento e teste. Elas tamb¨¦m oferecem uma maneira de assegurar que o ferramental de infraestrutura seja executado consistentemente, usando agentes de CI/CD em vez de esta??es de trabalho individuais. Nossos times t¨ºm tido bons resultado adotando essa t¨¦cnica em seus projetos.
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.
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.
