Releases: avast/gradle-docker-compose-plugin
Releases · avast/gradle-docker-compose-plugin
Service host guessing improved
Two major changes how the service host is guessed:
- Support for containers that connect to other container's network.
- Don't throw an exception when service gateway cannot be guessed - fallback to
localhost
instead. This solves issues with containers without networking.
projectNamePrefix option introduces
As requested in #231, it allows executing the same Gradle project concurrently.
Exposed port reloaded after TCP check failure
0.10.12 fix: forwarded port reloaded after failing check Fixes #229
Problems when a service is scaled to 0 instances solved
0.10.11 Fixed ServiceInfo when no service instances exist
checkContainersRunning option added
When this option is active (it is by default) then also checks if the container is running, when waiting for an open port or healthy state. So this is a fail-fast feature because it is obvious that the container will not open an port if it even doesn't run.
Table with exposed ports printed after composeUp finish
table with exposed ports printed after composeUp finish Fixes #186
Correct handling of InterruptedExceptions in Gradle before 5.0
This release fixes just cosmetics - any error message shouldn't be printed when finishing the build.
More information stored to the cache
The containers are now restarted also when docker-compose.yml
has been changed.
Exceptions after successful build removed from the log
0.10.6 fix: InterruptedException ignored when a daemon thread is interrupted…
Containers stopped correctly after failure with starting
This fixes an issue with calling docker-compose down
if the previous docker-compose up
failed.