Ignore exit-code when collecting outputs from containers

always ignore exit-code from docker-compose in thread that collects c…

…ontainers output Fixes #80

isRequired fixed - properties were not exposed correctly

0.6.12

isRequired fixed - properties were not exposed correctly

Remove containers of started services only

Explicitly rm containers from startedServices in ComposeDown if remov…

…eContainers=true (#136)

Calling 'down' would remove containers from all services defined in the
docker-compose file. If startedServices is used and
removeContainers=true, we instead only rm the containers from
startedServices.
The warning message is removed as it became obsolete.

Honour startedService when stopping, exitCodeFromService settings removed

0.6.10

exitCodeFromService settings removed - it cannot be applied Fixes #135

Handle output capturing when containers survive docker-compose

If containers are not stopped and docker-compose logs ends then it exits with 143. This is not an error state. Fixes #80

Support for --ignore-pull-failures

feat(composePull): add support for ignore-pull-failures arg (#127)

allow to skip failure as in docker-compose

Better failure handling

down on failed up because of healthcheck during compose up because of…

… dependencies between containers with condition "service_healthy"

Fix NullPointerException problem when ComposeUp fails

Improve behaviour in case of ComposeUp failure (#123)

* Fix NullPointerException when ComposeUp task fails

When the ComposeUp task fails, it tries to invoke the ComposeDown task.
This lead to a "java.lang.NullPointerException: Cannot invoke method
down() on null object" error due to an incorrect assignment order.

* Display correct health status when waitForHealthStateTimeout is exceeded

The health state was hard coded as 'starting', but it might also be
'unhealthy'.

Fix capturing of container log

Method renaming wasn't handled on all places.

Don't wait for open TCP ports of services that haven't been started

0.6.4

adjust field name