Arquillian Blog

Since we wrote this post we didn't laze around. Check our latest announcement.

The Arquillian team is proud to announce the 1.0.0.Alpha3 release of the Arquillian Cube Extension component!

What’s included in the Alpha3 release?

New Containerless DeployableContainer

When we’ve previously been talking about Containers we have been referring to Containers where the application is deployed inside a container. For example in the case of a Tomcat application, resources are deployed inside a Servlet container or in case of Apache TomEE you can deploy EJBs inside an EJB container.

But nowadays there are applications that contains the container (if they have one) embedded inside them. Typically these applications uses an embedded server and they are run directly from the commandline. Some examples can be Spring Boot, Netty, SparkJava or Undertow.

Arquillian Cube now has a ContainerLess DeployableContainer that combined with Docker can ‘deploy’ any application. This is not restricted to only Java applications, but can just as well be a Node or Ruby on Rails app.
For more information and examples see the documentation

Infer exposedPorts from portBindings

To simplify the configuration, Arquillian Cube will now auto export all ports
defined in the portBindings option. No need to specify them twice. In the case where
you want to remap the ports or only expose some of them, you can still define that
using the exposedPorts option.

For more information see the documentation

Allow connecting to a running container

With the configuration option shouldAllowToConnectToRunningContainers you can bypass
the Create/Start Cube commands if the a Docker Container with the same name is already
running on the target system. If so, Cube will reuse that Container moving forward.

This allow you to prestart the containers manually during development and just
connect to them to avoid the extra cost of starting the Docker Containers for each test
run. This assumes you are not changing the actual definition of the Docker Container itself.

What is Arquillian Cube Extension?

With Arquillian Cube you can control the lifecycle of Docker images as part of the test lifecyle, either automatically or manually. This gives you the chance to scale up from a integration/functional test level all the way up to the system test level.

Release details

Component	Arquillian Cube Extension
Version	1.0.0.Alpha3 view tag
Release date	2015-01-15
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.1.5.Final

Published artifacts org.arquillian.cube

• org.arquillian.cube » arquillian-cube-api jar javadoc pom
• org.arquillian.cube » arquillian-cube-spi jar javadoc pom
• org.arquillian.cube » arquillian-cube-docker jar javadoc pom
• org.arquillian.cube » arquillian-cube-containerless jar javadoc pom

Release notes and resolved issues 6

Bug

• #59 Create profiles in containerless module to allow to test both Node and Undertow
• #53 NPE in ping

Enhancement

• #54 Updates docker-java library to latest stable version
• #51 Add method to create Docker containers with CLI application
• #50 Infer exposedPorts from portBindings
• #44 Allow connecting to started Docker image

Thanks to the following list of contributors: Alex Soto, Aslak Knutsen, Karel Piwko