terraform/website/source/docs/enterprise/packer/builds/scheduling-builds.html.md

34 lines
1.6 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: "Schedule Periodic Builds"
2017-04-03 19:53:38 +02:00
sidebar_current: "docs-enterprise-packerbuilds-scheduling"
2017-03-22 18:31:44 +01:00
description: |-
Terraform Enterprise can automatically run a Packer build and create artifacts on a specified schedule.
2017-03-21 23:01:58 +01:00
---
2017-03-22 18:31:44 +01:00
# Schedule Periodic Builds in Terraform Enterprise
2017-03-21 23:01:58 +01:00
2017-03-22 18:31:44 +01:00
Terraform Enterprise can automatically run a Packer build and
2017-03-21 23:01:58 +01:00
create artifacts on a specified schedule. This option is disabled by default and can be enabled by an
2017-03-22 18:31:44 +01:00
organization owner on a per-[environment](/docs/enterprise/glossary#environment) basis.
2017-03-21 23:01:58 +01:00
2017-03-22 18:31:44 +01:00
On the specified interval, builds will be automatically queued that
run Packer for you, creating any artifacts and sending the appropriate
2017-03-21 23:01:58 +01:00
notifications.
If your artifacts are used in any other environments and you have activated
the plan on artifact upload feature, this may also queue Terraform
2017-03-21 23:01:58 +01:00
plans.
This feature is useful for maintenance of images and automatic updates,
or to build nightly style images for staging or development environments.
## Enabling Periodic Builds
2017-03-22 18:31:44 +01:00
To enable periodic builds for a build, visit the build settings page and select the desired interval and click the save button to persist the changes. An initial build may immediately run, depending
2017-03-21 23:01:58 +01:00
on the history, and then will automatically build at the specified interval.
If you have run a build separately, either manually or triggered from GitHub
2017-03-22 18:31:44 +01:00
or Packer configuration version uploads, Terraform Enterprise will not queue a new
build until the alloted time after the manual build ran. This ensures that a build has been executed at the specified schedule.