Building the Commerce Docker Images

You can build the Commerce Docker images after you build the Commerce Deployment package. This process is divided into two separate build jobs.

Building Core Docker Images

The build-core-images job builds Docker images from the Elastic Path Docker and CloudOps for Kubernetes repositories. This job builds the following images:

• Java base image
• Tomcat base image
• ActiveMQ image
• MySQL image
• Commerce deployment information page image

Run the job to build all the preceding images for the first time. If you make changes, you might need to run the job again. This applies to the Elastic Path Docker repository and the Commerce deployment information page Dockerfile in the CloudOps for Kubernetes repository.

Jenkins job parameters

The following parameters are available in the Jenkins job build-core-images:

imageTag

The value to tag the built Docker images. Ensure that the value is a valid Docker tag.

tomcatVersion

The Tomcat version to use when building the Elastic Path Tomcat base image.

cloudOpsForKubernetesBranch

The CloudOps for Kubernetes branch to use for the Jenkinsfile that defines how the Docker images are built.

dockerBranch

The Elastic Path Docker branch to use for the Bash scripts and Dockerfile templates that define how the Docker images are built.

Building Self Managed Commerce Docker Images

The build-commerce-images job builds Self Managed Commerce application images. This job builds the following Elastic Path images:

• Cortex
• Commerce Manager (cm)
• Integration
• Search
• Batch
• Wiremock (mock)
• Data Sync Tool (data-sync)
• Data Population Tool (data-pop-tool)

Run this job to build Commerce images using the Elastic Path Docker repository and a Self Managed Commerce deployment package built using the build-deployment-package job.

Jenkins Job Parameters

The following parameters are available in the Jenkins job build-commerce-images:

imageTag

The value to tag the built Docker images. Ensure that the value is a valid Docker tag.

tomcatVersion

The version of Elastic Path Tomcat base image to use as a base Docker image.

note

The build-core-images job must be run at least once first with the same value.

cloudOpsForKubernetesBranch

The CloudOps for Kubernetes branch to use for the Jenkinsfile that defines how the Docker images are built.

dockerBranch

The Elastic Path Docker branch to use for the Bash scripts and Dockerfile templates that define how the Docker images are built.

epCommerceBranch

The Self Managed Commerce branch to use when you download the Commerce deployment package. The package contains the application binaries that are built into the Docker images.

note

The build-deployment-package job must be run at least once first with the same value.

Next Steps

After you build the Docker images, see the Deploy Commerce documentation.