2017-03-21 23:01:58 +01:00
|
|
|
---
|
2017-03-22 18:31:44 +01:00
|
|
|
layout: "packer"
|
|
|
|
page_title: "Running Packer Builds"
|
|
|
|
sidebar_current: "docs-enterprise-packer-builds-runbuilds"
|
|
|
|
description: |-
|
|
|
|
This briefly covers the internal process of running builds in Terraform Enterprise.
|
2017-03-21 23:01:58 +01:00
|
|
|
---
|
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
# How Packer Builds Run in Terraform Enterprise
|
2017-03-21 23:01:58 +01:00
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
This briefly covers the internal process of running builds in Terraform Enterprise. It's
|
2017-03-21 23:01:58 +01:00
|
|
|
not necessary to know this information, but may be valuable to
|
2017-03-22 18:31:44 +01:00
|
|
|
help understand implications of running or debugging failing
|
2017-03-21 23:01:58 +01:00
|
|
|
builds.
|
|
|
|
|
|
|
|
### Steps of Execution
|
|
|
|
|
|
|
|
1. A Packer template and directory of files is uploaded via Packer Push or GitHub
|
2017-03-22 18:31:44 +01:00
|
|
|
2. Terraform Enterprise creates a version of the build configuration and waits for the upload
|
2017-03-21 23:01:58 +01:00
|
|
|
to complete. At this point, the version will be visible in the UI even if the upload has
|
|
|
|
not completed
|
2017-03-22 18:31:44 +01:00
|
|
|
3. Once the upload finishes, the build is queued. This is potentially
|
2017-03-21 23:01:58 +01:00
|
|
|
split across multiple machines for faster processing
|
2017-03-22 18:31:44 +01:00
|
|
|
4. In the build environment, the package including the files and Packer template
|
2017-03-21 23:01:58 +01:00
|
|
|
are downloaded
|
2017-03-22 18:31:44 +01:00
|
|
|
5. `packer build` is run against the template in the build environment
|
|
|
|
6. Logs are streamed into the UI and stored
|
|
|
|
7. Any artifacts as part of the build are then uploaded via the public
|
|
|
|
artifact API, as they would be if Packer was executed locally
|
|
|
|
8. The build completes, the environment is teared down and status
|
|
|
|
updated
|
2017-03-21 23:01:58 +01:00
|
|
|
|