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: "Managing Packer Versions"
|
2017-04-03 19:53:38 +02:00
|
|
|
sidebar_current: "docs-enterprise-packerbuilds-versions"
|
2017-03-22 18:31:44 +01:00
|
|
|
description: |-
|
|
|
|
Terraform Enterprise does not automatically upgrade the version of Packer used to run builds or compiles.
|
2017-03-21 23:01:58 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
# Managing Packer Versions
|
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
Terraform Enterprise does not automatically upgrade the version of Packer
|
2017-03-21 23:01:58 +01:00
|
|
|
used to run builds or compiles. This is intentional, as occasionally
|
|
|
|
there can be backwards incompatible changes made to Packer that cause templates to stop
|
|
|
|
building properly, or new versions that produce some other unexpected behavior.
|
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
All upgrades must be performed by a user, but Terraform Enterprise will display a notice
|
2017-03-21 23:01:58 +01:00
|
|
|
above any builds run with out of date versions. We encourage the use
|
|
|
|
of the latest version when possible.
|
|
|
|
|
|
|
|
### Upgrading Packer
|
|
|
|
|
|
|
|
1. Go the Settings tab of a build configuration or application
|
2017-03-22 18:31:44 +01:00
|
|
|
2. Go to the "Packer Version" section and select the version you
|
2017-03-21 23:01:58 +01:00
|
|
|
wish to use
|
2017-03-22 18:31:44 +01:00
|
|
|
3. Review the changelog for that version and previous versions
|
|
|
|
4. Click the save button. At this point, future builds will use that
|
2017-03-21 23:01:58 +01:00
|
|
|
version
|