github.com/danp/terraform@v0.9.5-0.20170426144147-39d740081351/website/source/docs/enterprise/packer/builds/how-builds-run.html.md (about)

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