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

Support testing collections with deps using --docker #59563

mattclay opened this issue Jul 24, 2019 · 3 comments


Copy link

commented Jul 24, 2019


Running tests on collections which have dependencies with the --docker option is not currently supported. Only the collection being tested is copied into the container.

All collections in the same collection root should be copied into the container. Support for dependencies in other collection roots will not be supported. It will be up to the user to make sure all the necessary dependencies are already installed in the same collection root. If unnecessary collections are present, those will be copied as well.


Feature Idea



@mattclay mattclay self-assigned this Jul 24, 2019

@mattclay mattclay added this to To do in Testing Collections via automation Jul 24, 2019


This comment has been minimized.

Copy link

commented Jul 24, 2019

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help


This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2019

This change should also include updates to the layout when using --docker. The current layout is:

  • ~/ansible/ - ansible source
  • ~/ansible/ansible_collections/ - collections

The new layout should be:

  • ~/{working_dir}/ansible/ - ansible source
  • ~/{working_dir}/ansible_collections/ - collections

This will avoid nesting the collections inside the ansible source, keeping the layout separate, as it would be if not using the --docker option.

@mattclay mattclay removed the needs_triage label Jul 25, 2019


This comment has been minimized.

Copy link

commented Aug 7, 2019

+1 Most of my integration tests would need this feature, it's annoying having to put roles into place in CI manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.