» How Packer Builds Run in Terraform Enterprise
Deprecation warning: The Packer, Artifact Registry and Terraform Enterprise (Legacy) features of Atlas will no longer be actively developed or maintained and will be fully decommissioned on Thursday, May 31, 2018. Please see our Upgrading From Terraform Enterprise (Legacy) guide to migrate to the new Terraform Enterprise and our guide on building immutable infrastructure with Packer on CI/CD for ideas on implementing the Packer and Artifact features yourself.
This briefly covers the internal process of running builds in Terraform Enterprise. It's not necessary to know this information, but may be valuable to help understand implications of running or debugging failing builds.
» Steps of Execution
A Packer template and directory of files is uploaded via Packer Push or GitHub
Terraform Enterprise creates a version of the build configuration and waits for the upload to complete. At this point, the version will be visible in the UI even if the upload has not completed
Once the upload finishes, the build is queued. This is potentially split across multiple machines for faster processing
In the build environment, the package including the files and Packer template are downloaded
packer buildis run against the template in the build environment
Logs are streamed into the UI and stored
Any artifacts as part of the build are then uploaded via the public artifact API, as they would be if Packer was executed locally
The build completes, the environment is teared down and status updated