terraform/website/source/docs/enterprise/packer/builds/index.html.md

32 lines
1.3 KiB
Markdown
Raw Normal View History

2017-03-21 23:01:58 +01:00
---
2017-04-03 19:53:38 +02:00
layout: "enterprise"
2017-03-22 18:31:44 +01:00
page_title: "About Builds"
2017-04-03 19:53:38 +02:00
sidebar_current: "docs-enterprise-packerbuilds"
2017-03-22 18:31:44 +01:00
description: |-
Builds are instances of `packer build` being run within Terraform Enterprise.
2017-03-21 23:01:58 +01:00
---
# About Builds
2017-03-22 18:31:44 +01:00
Builds are instances of `packer build` being run within Terraform Enterprise. Every
2017-03-21 23:01:58 +01:00
build belongs to a build configuration.
__Build configurations__ represent a set of Packer configuration versions and
2017-03-22 18:31:44 +01:00
builds run. It is used as a namespace within Terraform Enterprise, Packer commands and URLs. Packer
configuration sent to Terraform Enterprise are stored and versioned under
2017-03-21 23:01:58 +01:00
these build configurations.
These __versions__ of Packer configuration can contain:
- The Packer template, a JSON file which define one or
more builds by configuring the various components of Packer
- Any provisioning scripts or packages used by the template
2017-03-22 18:31:44 +01:00
- Applications that use the build as part of the pipeline and merged into the version prior to running Packer on it
2017-03-21 23:01:58 +01:00
2017-03-22 18:31:44 +01:00
When a new version of Packer configuration and associated
scripts from GitHub or `packer push` is received, it automatically starts a new
2017-03-21 23:01:58 +01:00
Packer build. That Packer build runs in an isolated machine environment with the contents
of that version available to it.
2017-03-22 18:31:44 +01:00
You can be alerted of build events with [Build Notifications](/docs/enterprise/packer/builds/notifications.html).