iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

use absolute links

This commit is contained in:
Matthew Hooker 2017-12-11 14:37:28 -08:00
parent be3f0a121a
commit 97bacf6790
No known key found for this signature in database
GPG Key ID: 7B5F933D9CE8C6A1
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/guides/packer-on-cicd/build-image-in-cicd.html.md
View File

@ -11,6 +11,6 @@ The following guides from our partners show how to use their services to build i
- How to Build Immutable Infrastructure with Packer and CircleCI Workflows (coming soon)
- [Using Packer and Ansible to Build Immutable Infrastructure in CodeShip](https://blog.codeship.com/packer-ansible/)
The majority of the [Packer Builders](../../docs/builders/index.html) can run in a container or VM, a common model used by most CI/CD services. However, the [QEMU builder](../../docs/builders/qemu.html) for [KVM](https://www.linux-kvm.org/page/Main_Page) and [Xen](https://www.xenproject.org/) virtual machine images, [VirtualBox builder](../../docs/builders/virtualbox.html) for OVA or OVF virtual machines and [VMWare builder](../../docs/builders/vmware.html) for use with VMware products require running on a bare-metal machine.
The majority of the [Packer Builders](/docs/builders/index.html) can run in a container or VM, a common model used by most CI/CD services. However, the [QEMU builder](/docs/builders/qemu.html) for [KVM](https://www.linux-kvm.org/page/Main_Page) and [Xen](https://www.xenproject.org/) virtual machine images, [VirtualBox builder](/docs/builders/virtualbox.html) for OVA or OVF virtual machines and [VMWare builder](/docs/builders/vmware.html) for use with VMware products require running on a bare-metal machine.
The [Building a VirtualBox Image with Packer in TeamCity](./building-virtualbox-image.html) guide shows how to create a VirtualBox image using TeamCity's support for running scripts on bare-metal machines.
The [Building a VirtualBox Image with Packer in TeamCity](/guides/packer-on-cicd/building-virtualbox-image.html) guide shows how to create a VirtualBox image using TeamCity's support for running scripts on bare-metal machines.

4
website/source/guides/packer-on-cicd/build-virtualbox-image.html.md
View File

@ -8,7 +8,7 @@ page_title: Build a VirtualBox Image with Packer in TeamCity
This guide walks through the process of building a VirtualBox image using Packer on a new TeamCity Agent. Before getting started you should have access to a TeamCity Server.
The Packer VirtualBox builder requires access to VirtualBox, which needs to run on a bare-metal machine as virtualization is generally not supported on cloud instances. This is also true for the [VMWare](../../docs/builders/vmware.html) and the [QEMU](../../docs/builders/qemu.html) Packer builders.
The Packer VirtualBox builder requires access to VirtualBox, which needs to run on a bare-metal machine as virtualization is generally not supported on cloud instances. This is also true for the [VMWare](/docs/builders/vmware.html) and the [QEMU](/docs/builders/qemu.html) Packer builders.
## 1. Provision a Bare-metal Machine
@ -85,7 +85,7 @@ In the **Script content** field add the following:
/root/packer build -only=virtualbox-iso -var "headless=true" ./packer.json
```
This will use the `build` command in Packer to build the image defined in `./packer.json`. It assumes that `packer.json` is the Packer build configuration file in the root path of the VCS repository. Packer defaults to building VirtualBox virtual machines by launching a GUI that shows the console, since this will run in CI/CD, the the [`headless` variable](../../docs/builders/virtualbox-iso.html#headless) instructs Packer to start the machine without the console. Packer can build multiple image types, so the [`-only=virtualbox-iso` option](../../docs/commands/build.html#only-foo-bar-baz) instructs Packer to only build the builds with the name `virtualbox-iso`.
This will use the `build` command in Packer to build the image defined in `./packer.json`. It assumes that `packer.json` is the Packer build configuration file in the root path of the VCS repository. Packer defaults to building VirtualBox virtual machines by launching a GUI that shows the console, since this will run in CI/CD, the the [`headless` variable](/docs/builders/virtualbox-iso.html#headless) instructs Packer to start the machine without the console. Packer can build multiple image types, so the [`-only=virtualbox-iso` option](/docs/commands/build.html#only-foo-bar-baz) instructs Packer to only build the builds with the name `virtualbox-iso`.
## 6. Run a build in TeamCity

6
website/source/guides/packer-on-cicd/index.html.md
View File

@ -8,6 +8,6 @@ page_title: Build Immutable Infrastructure with Packer in CI/CD
This guide focuses on the following workflow for building immutable infrastructure. This workflow can be manual or automated and it can be implemented with a variety of technologies. The goal of this guide is to show how this workflow can be fully automated using Packer for building images from a continuous integration/continuous deployment (CI/CD) pipeline.
1. [Build Images using Packer in CI/CD](./build-image-in-cicd.html)
2. [Upload the new image to S3](./upload-images-to-artifact.html) for future deployment or use during development
3. [Create new Terraform Enterprise runs](./triggering-tfe.html) to provision new instances with the images
1. [Build Images using Packer in CI/CD](/guides/packer-on-cicd/build-image-in-cicd.html)
2. [Upload the new image to S3](/guides/packer-on-cicd/upload-images-to-artifact.html) for future deployment or use during development
3. [Create new Terraform Enterprise runs](/guides/packer-on-cicd/trigger-tfe.html) to provision new instances with the images