Testing Packer changes

[Chris Forbes]

I'm keen to start testing my Packer repositories as part of CI. There is the simple check of running packer validate, which is a good first step for ensuring syntax and config is good. What I would like to start doing is building my images on any change. If the build runs to completion, then clearly the scripts haven't hit a failure point. This doesn't mean that the machine is fit for purpose, however.

Does anyone have any suggestions on testing a machine during the Packer process?

[Rickard von Essen]

I would run packer build in one step and then launch a VM from that image running some tests with something like serverspec and if it passes the test promote the image.

On 9 June 2017 at 14:59, Chris Forbes <kitf...@gmail.com> wrote:

I'm keen to start testing my Packer repositories as part of CI. There is the simple check of running packer validate, which is a good first step for ensuring syntax and config is good. What I would like to start doing is building my images on any change. If the build runs to completion, then clearly the scripts haven't hit a failure point. This doesn't mean that the machine is fit for purpose, however.

Does anyone have any suggestions on testing a machine during the Packer process?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/883cce81-dbdb-48ed-9e77-7a552b389d10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.