Building the Commerce Container Images
You can build the Commerce container images after you build the Commerce Deployment package. This process is divided into two separate build jobs.
Building Core Container Images
The build-core-images job builds container 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 container images. Ensure that the value is a valid Docker tag.
note
The imageTag value does not apply to the Java base image or the Tomcat base image.
mysqlVersion
The MySQL version to use when building the MySQL container image. The supported options are 5.7 and 8.0.
cloudOpsForKubernetesBranch
The CloudOps for Kubernetes branch to use for the Jenkinsfile that defines how the container images are built.
dockerBranch
The Elastic Path Docker branch to use for the Bash scripts and Dockerfile templates that define how the container images are built.
epCommerceBranch
The Commerce branch to use when building Commerce related artifacts.
Building Self Managed Commerce Container 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 container images. Ensure that the value is a valid Docker tag.
cloudOpsForKubernetesBranch
The CloudOps for Kubernetes branch to use for the Jenkinsfile that defines how the container images are built.
dockerBranch
The Elastic Path Docker branch to use for the Bash scripts and Dockerfile templates that define how the container 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 container images.
note
The build-deployment-package job must be run at least once first with the same value.
Next Steps
After you build the container images, see the Deploy Commerce documentation.