Skip to content
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

Merged
merged 1 commit into from
May 13, 2018

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Feb 23, 2018

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.

Copy link
Contributor

@vinzent vinzent left a 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 ?

@ekohl
Copy link
Member Author

ekohl commented Feb 26, 2018

I do miss however documentation if something changes when someone wants invoke beaker.

I'm waiting to see how the beaker-hostgenerator PR turns out. Right now you replace BEAKER_nodeset=docker/centos-7 with BEAKER_setfile=centos7-64{hypervisor=docker} but I'm considering a PR for to set the hypervisor via an env var. Sadly the invocation is a bit spread over beaker.

And where are these docker_image_commands now ? are they default in beaker-hostgenerator ?

Yes. I'm hoping that our defaults are good enough defaults for the entire community :)

@ekohl ekohl force-pushed the beaker-hostgenerator branch from fd10573 to 923c21a Compare April 10, 2018 11:52
@ekohl
Copy link
Member Author

ekohl commented Apr 10, 2018

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 docker_sets. We also need to git rm -r spec/acceptance/nodesets/docker in every module when syncing since modulesync can't remove old files.

This also removes sudo: required and dist: trusty since that's implied
by Travis when using docker.
@ekohl ekohl force-pushed the beaker-hostgenerator branch from 923c21a to 644c714 Compare May 13, 2018 11:13
This was referenced May 13, 2018
@ekohl
Copy link
Member Author

ekohl commented May 13, 2018

Updated. I submitted a bunch of PRs (linked) for the modules that actually use docker_sets. For other modules I've some commits ready that purge the files and clean up .sync.yml for windows modules which had the docker files marked as unmanaged. When this is merged I'll submit those.

@bastelfreak bastelfreak merged commit 2d81b20 into voxpupuli:master May 13, 2018
@ekohl ekohl deleted the beaker-hostgenerator branch May 13, 2018 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants