The Elastic Path Commerce build and continuous integration (CI) processes generate several deployable artifacts. This topic describes the artifacts and their relationship.
Elastic Path Commerce Container Images
The Elastic Path Commerce container images are the images that run the Elastic Path Commerce application services and tools. You can build these images using tools provided by Elastic Path. Each container image is created by adding Java binaries and other files from the deployment package to one of the base images. For more information, see Containers Overview.
The base images are container images that are used either as the foundation for the Elastic Path Commerce container images, or images that can be used to run non-Elastic Path Commerce services such as ActiveMQ and MySQL. These images do not contain or run Elastic Path Commerce application code. You build these images using tools provided by Elastic Path. For more information, see Containers Overview.
The Elastic Path Commerce deployment package is an artifact that you build from the Elastic Path Commerce
ep-commerce application source code. It is created by a Maven build process and is a Zip file that contains the following:
- The Java Web Archive (WAR) and configuration files for each of the Elastic Path Commerce applications.
- The Java binaries of various Elastic Path Commerce tools.
- The Liquibase files used to create and populate an Elastic Path Commerce database.
ops-spec.jsonfile that defines required external dependencies, such as Java version, Maven version, ActiveMQ version, and Tomcat version.
The deployment package is required to build the Elastic Path Commerce application container images. For information on building the deployment package, see Build Deployment Package.
The following diagram describes the relationship between the artifacts.