public interface ShutdownStrategy
Modifier and Type | Field and Description |
---|---|
static ShutdownStrategy |
AGGRESSIVE
Deprecated.
Use
KILL_DOWN (the default strategy) |
static ShutdownStrategy |
AGGRESSIVE_WITH_NETWORK_CLEANUP
Deprecated.
Use
KILL_DOWN (the default strategy) |
static ShutdownStrategy |
GRACEFUL
Call docker-compose down, kill, then rm.
|
static ShutdownStrategy |
KILL_DOWN
Call docker-compose kill then down.
|
static ShutdownStrategy |
SKIP
Skip shutdown, leaving containers running after tests finish executing.
|
Modifier and Type | Method and Description |
---|---|
void |
shutdown(DockerCompose dockerCompose,
Docker docker) |
@Deprecated static final ShutdownStrategy AGGRESSIVE
KILL_DOWN
(the default strategy)@Deprecated static final ShutdownStrategy AGGRESSIVE_WITH_NETWORK_CLEANUP
KILL_DOWN
(the default strategy)static final ShutdownStrategy GRACEFUL
With this strategy, you will need to take care not to accidentally write images that ignore their down signal, for instance by putting their run command in as a string (which is interpreted by a SIGTERM-ignoring bash) rather than an array of strings.
static final ShutdownStrategy KILL_DOWN
static final ShutdownStrategy SKIP
You can use this option to speed up repeated test execution locally by leaving images up between runs. Do not commit it! You will be potentially abandoning long-running processes and leaking resources on your CI platform!
void shutdown(DockerCompose dockerCompose, Docker docker) throws IOException, InterruptedException
IOException
InterruptedException
Copyright © 2019 Pivotal Software, Inc.. All rights reserved.