A Vagrant+Ansible automated test project #542
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This provides a new test project in the `test-project-play-rpm` directory. It is the default Play 2.3.x sample project packaged as an RPM. The build and test environment uses a Centos-6.6 VM, managed with Vagrant and provisioned with Ansible (see the vagrant file and `provisioning/site.yml`). The the package building and tests are also orchestrated with Ansible (see `provisioning/test.yml`). The tests run performs the following: - compile and build rpm package - install the built rpm - check that server is running and responding after install - check that service can restart - and is responding after restart - uninstall the rpm
|
Note, this PR depends on #541 |
|
Nice. How do you run the semi-automated tests? I'm fairly new to |
avoid substitution issues by excluding sbt-native-packager from Play’s sbt-plugin
|
Ah, I guess a readme is probably in order. Ansible can be installed through a bunch of different package managers: The Vagrant file invokes Ansible as a ‘provisioner’ The |
| # the path on the guest to mount the folder. And the optional third | ||
| # argument is a set of non-required options. | ||
| # config.vm.synced_folder "../data", "/vagrant_data" | ||
| config.vm.synced_folder "..", "/vagrant" |
There was a problem hiding this comment.
This will sync the complete sbt-native-packager project directory, rather than just this test subdirectory.
|
Works fine for me. I'll merge this and add your instructions. |
muuki88
added a commit
that referenced
this pull request
Apr 6, 2015
A Vagrant+Ansible automated test project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This provides a new test project in the
test-project-play-rpmdirectory. It is the default Play 2.3.x sample project packaged as an RPM.The build and test environment uses a Centos-6.6 VM, managed with Vagrant and provisioned with Ansible (see the vagrant file and
provisioning/site.yml).The the package building and tests are also orchestrated with Ansible (see
provisioning/test.yml).The test run (run-test-playbook.sh) performs the following: