terratest-maven-plugin VS jib

The terratest-maven-plugin is now featured on terratest's website (see: https://terratest.gruntwork.io/docs/testing-best-practices/tools-and-plugins/) :) So if you have any questions or would like to learn more, visit: https://terratest-maven-plugin.github.io or the GitHub repository: https://github.com/terratest-maven-plugin/terratest-maven-plugin

I have created a maven plugin project for running our terratests inside our traditional maven build pipeline. This has helped our team to have a one-stop-shop for running integration and unit tests and reasoning about our infrastructure. If you interested check out here: https://github.com/terratest-maven-plugin/terratest-maven-plugin and for a quick overview: https://terratest-maven-plugin.github.io

You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:

JIB

It is pretty easy to do with https://github.com/GoogleContainerTools/jib.

Save yourself the dockerfile and use jib: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin

I first learned about Distroless because it was the default option in Google's Jib. Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now.

Optimize your Dockerfile by using a small base Java Image, use either Spring Boot's layers tools or Google Jib to build your docker file, and increase CPU/Memory requests and limits if you can.

In this section, we will setup the automated generation and deployment of a Docker container image. You will need a Docker Hub account and the Jib Gradle Plugin.

If you don't want to hack on your own scripts to package your app into a container, I can recommend the JIB maven plugin. A gradle version is also available.