New profile 'wildfly-docker-maven' for testing with rhuss/docker-maven-plugin #297
Conversation
This file contains hidden or 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 profile demonstrates the usage of a docker-maven-plugin for starting a Docker container for integration tests (without Arquillian). It has been tested with the example 'simple-servlet'. The image created contains the deployment artifact already which is copied to `/opt/wildfly/standalone/deployments` so no extra deployment step is required. To test it simply call: mvn -f servlet/simple-servlet/pom.xml -Pwildfly-docker-maven clean install (assuming your DOCKER_HOST variable is set properly). One can also build the image, start and stop it separately: mvn -f servlet/simple-servlet/pom.xml -Pwildfly-docker-maven package docker:build mvn -f servlet/simple-servlet/pom.xml -Pwildfly-docker-maven docker:start mvn -f servlet/simple-servlet/pom.xml -Pwildfly-docker-maven docker:stop It use dynamically assigned ports, so multiples test can be run in parallel.
arun-gupta
added a commit
that referenced
this pull request
Apr 21, 2015
New profile 'wildfly-docker-maven' for testing with rhuss/docker-maven-plugin
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 profile demonstrates the usage of docker-maven-plugin for starting a Docker container for integration tests (without Arquillian). It has been tested with the example 'simple-servlet', for which the single unit test has be duplicated to work without Arquillian. The profile uses the
maven-failsafe-plugin(triggered on*IT.javaclasses) and switched offmaven-surefire-pluginso that the two tests don't interfere.The image created contains the deployment artifact already which is copied to
/opt/wildfly/standalone/deploymentsso no extra deployment step is required.To test it simply call:
(assuming your DOCKER_HOST variable is set properly). One can also build the image, start and stop it separately:
It use dynamically assigned ports, so multiples test can be run in parallel.
Please note that its quite simplistic and doesn't use all feature of the plugin. Some comments has been added inline to explain the various pieces, for more information please refer to the user manual
What is not shown is how to push the combined image to a registry with
docker:push. For this to work, the credentials should be added to~/.m2/settings.xmland the name of the image should be adapted accordingly to the docker hub conventions (user/repo:tag)