This repository has been archived by the owner on Jan 24, 2018. It is now read-only.
Test sirbot & website ansible deployment with travis #6
Labels
Comments
seanson
pushed a commit
that referenced
this issue
May 20, 2017
Issue #6 This commit changes the Travic CI pipeline to run ansible in a docker container and additionally tests the deployment tasks. .
seanson
pushed a commit
that referenced
this issue
May 20, 2017
Issue #6 This commit changes the Travic CI pipeline to run ansible in a docker container and additionally tests the deployment tasks. Updated README.md to contain new test script
seanson
pushed a commit
that referenced
this issue
May 20, 2017
Issue #6 This commit changes the Travic CI pipeline to run ansible in a docker container and additionally tests the deployment tasks. Updated README.md to contain new test script
Merged
mattrasband
pushed a commit
that referenced
this issue
May 22, 2017
Issue #6 This commit changes the Travic CI pipeline to run ansible in a docker container and additionally tests the deployment tasks. Updated README.md to contain new test script
|
Tests doesn't seems to be running properly |
|
I think this will not be possible for PRs as there is no effective way to hide the vault password |
|
Can we have a testing specific vault, or none for testing? I think if we set up another group we could get away with it (but we may need to remove globally scoped variables in that case...) |
|
What I understand is that ansible try to open the vaults of every group there is in your inventory. Even is the current target is not in these groups. One thing I saw is people putting the vault elsewhere and include them only for some hosts. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment travis only check the setup-server and python roles
The text was updated successfully, but these errors were encountered: