Before You Begin
Review the Introduction section to obtain an overview of the CloudOps for Kubernetes solution.
Building Elastic Path Commerce Docker Images
Elastic Path Commerce environments are deployed using Docker images built by provided Jenkins jobs. Those Docker images must exist before you can deploy an Elastic Path Commerce environment.
When you want to deploy Elastic Path Commerce (
ep-commerce) source code to an Elastic Path Commerce environment you must first build the deployment package for the desired
ep-commerce branch, then build Docker images from that deployment package. At a very high level, the steps are:
- Identify the
ep-commercebranch to build
- Build the deployment package
- Build the docker images
- Deploy or update an Elastic Path Commerce environment
There are three approaches to ensuring the required Docker images are available, discussed below.
Call the Build Jobs Directly
Information about the Jenkins job that builds the Commerce deployment package is available in the Build Deployment Packages section.
Information about the Jenkins jobs used to build Docker images is available in the Build Commerce Docker Images section.
Use the Convenience Jobs
Some convenience jobs are provided to simplify several of the steps required to build, test, deploy and update Elastic Path Commerce code and environments. These include the ability to build the Elastic Path Commerce deployment package and all required Docker images.
commerce-test-and-deploy Jenkins Job
commerce-test-and-deploy Jenkins job to build the Elastic Path Commerce deployment package and Docker images, and use those to deploy or update a full Elastic Path Commerce environment suitable for development. For more information, see the Elastic Path Commerce CI Pipelines documentation.
multi-purpose-commerce-tool Jenkins Job
multi-purpose-commerce-tool Jenkins job to build the Elastic Path Commerce deployment package and Docker images, and use those to deploy or update a full Elastic Path Commerce environment. This job exposes many options and provides a lot of flexibility regarding what you want to do and how you want it done. For more information, see the Multi-purpose Commerce Tool documentation.
commerce-branch-validation Jenkins Job
commerce-branch-validation Jenkins job to build the Elastic Path Commerce deployment package and Docker images, and use those to temporariliy deploy an Elastic Path Commerce environment while automated tests are run against it. For more information, see the Elastic Path Commerce CI Pipelines documentation.
Pull the Images from Another Account
If you have multiple CloudOps for Kubernetes accounts, you may prefer to build and validate your Elastic Path Commerce Docker images in one account and promote those images to another account. Jenkins jobs are provided to facilitate this. For more information see Promote Images Between Docker Repositories.