-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use beaker-hostgenerator for docker acceptance tests #453
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good move to use beaker-hostgenerator.
I do miss however documentation if something changes when someone wants invoke beaker.
And where are these docker_image_commands
now ? are they default in beaker-hostgenerator ?
I'm waiting to see how the beaker-hostgenerator PR turns out. Right now you replace
Yes. I'm hoping that our defaults are good enough defaults for the entire community :) |
fd10573
to
923c21a
Compare
Updated now that the beaker-hostgenerator change was released. See voxpupuli/puppet-autofs#118 for an example that is now required for every module that uses |
This also removes sudo: required and dist: trusty since that's implied by Travis when using docker.
923c21a
to
644c714
Compare
Updated. I submitted a bunch of PRs (linked) for the modules that actually use |
Depends on voxpupuli/beaker-hostgenerator#109 and will require changes to modules with docker tests. Also allows removal of the files in the actual containers.
It'd be nice if we could also push the EC2 and vagrant boxes into beaker-hostgenerator.