springtainer-redis

Dependency

<dependency>
  <groupId>com.avides.springboot.springtainer</groupId>
  <artifactId>springtainer-redis</artifactId>
  <version>2.0.0</version>
  <scope>test</scope>
</dependency>

Configuration

Properties consumed (in bootstrap.properties):

• embedded.container.redis.enabled (default is true)
• embedded.container.redis.startup-timeout (default is 30)
• embedded.container.redis.docker-image (default is redis:6.2.22-alpine)
• embedded.container.redis.port (default is 6379)

Properties provided (in application-it.properties):

• embedded.container.redis.host
• embedded.container.redis.port

Example for minimal configuration in application-it.properties:

spring.redis.host=${embedded.container.redis.host} 
spring.redis.port=${embedded.container.redis.port}

Spring's test-context cache is bounded automatically

spring.test.context.cache.maxSize=1 ships as a classpath spring.properties resource inside springtainer-common itself, so it's picked up automatically for every consumer - no configuration needed on your side. This bounds Spring's test-context cache so a no-longer-current context (and, via its ContextClosedEvent listener, its embedded container) gets evicted and cleanly closed as soon as a differently-configured context needs the slot, instead of piling up unclosed until the whole JVM exits.

This works the same way whether tests are launched via Maven Surefire/Failsafe or directly from an IDE's own test runner (e.g. Eclipse), since Spring resolves it from the classpath (org.springframework.core.SpringProperties) rather than from a JVM system property.

Logging

To reduce logging insert this into the logback-configuration:

<!-- Springtainer -->
<logger name="com.github.dockerjava" level="WARN" />

Labels

The container exports multiple labels to analyze running springtainers:

• SPRINGTAINER_SERVICE=redis
• SPRINGTAINER_IMAGE=${embedded.container.redis.docker-image}
• SPRINGTAINER_STARTED=$currentTimestamp