0.32.1

• Better errors that tell you why your http checking healthcheck has failed, rather than just that it has failed.

0.32.0

#177: Add support for new YY.MM docker version format. (thanks @samwright!)
#164: Improved logging for Retryer.
#171: Fix regex for splitting on newline characters to work on Windows too. (thanks @samwright!)
#168: Deprecate Aggressive shutdown strategies.

0.31.1

This release fixes a regression in Windows support introduced in v0.31.0 (#166).

0.31.0 — Native docker healthchecks

docker-compose-rule will now wait for containers to become healthy, as specified in the docker image or in the docker-compose config, before running tests. This allows users to fold their healthchecks into their Docker container specification, letting the team that releases the Docker image determine what makes their service healthy, rather than having each downstream product reinvent the wheel.

Note that you will need to upgrade to at least docker 1.12.0 and docker-compose 1.10.0 to use native healthchecks.

0.30.0

This release adds new options to:

• pull images on startup
• treat status code 404 as unhealthy

It also adds the following performance improvements:

• Containers are now killed by defaut at test end, rather than stopped, as most images ignore the stop signal, incurring an unnecessary 10 second delay per test. Tests can explicitly specify ShutdownStrategy.GRACEFUL if for any reason you still need the old behaviour.
• Docker For Mac users will now be warned if their /etc/hosts configuration looks bad. This issue can affect test performance by an order of magnitude.

0.29.1

Two artifacts will now be published: docker-compose-rule-core and docker-compose-rule-junit4. Depending on the latter should provide the same interface as can currently be used through junit.

Split into two separate projects

Two artifacts will now be published: docker-compose-rule-core and docker-compose-rule-junit4. Depending on the latter should provide the same interface as can currently be used through junit.

0.28.1

If you're using docker-compose syntax V2, use ShutdownStrategy.AGGRESSIVE_WITH_NETWORK_CLEANUP to ensure networks are cleaned up appropriately. Thanks to @ashrayjain for the PR!

(Identical to 0.28.0 due to publish failure)

Note: As of 0.30.0, we recommend using the default shutdown strategy.

0.27.1

Fixed #131 "DockerMachine fails if "system" and "additional" environment variables are duplicated", thanks @gsheasby!

0.27.0

• Log collection now uses the more accurate docker-compose config --services instead of docker ps (thanks to @dev-kpyc!)
• New DockerComposeExecOption.noOptions() helper method.
• All methods on DockerComposeRule.Builder are now 'strict', to avoid accidentally mutating earlier calls when building.