Overview of Self Managed Commerce Builds
Before You Begin
Review the Introduction section to obtain an overview of the CloudOps for Kubernetes solution.
Building Self Managed Commerce Container Images
Self Managed Commerce environments are deployed using container images built by provided Jenkins jobs. Those container images must exist before you can deploy a Self Managed Commerce environment.
When you want to deploy Self Managed Commerce (ep-commerce) source code to a Self Managed Commerce environment you must first build the deployment package for the desired ep-commerce branch, then build container 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 container images
- Deploy or update a Self Managed Commerce environment
Three approaches are available to ensure the required container images are accessible, as 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 container images is available in the Build Commerce Container Images section.
Use the Convenience Jobs
Some convenience jobs are provided to simplify several of the steps required to build, test, deploy and update Self Managed Commerce code and environments. These include the ability to build the Self Managed Commerce deployment package and all required container images.
The commerce-test-and-deploy Jenkins Job
Use the commerce-test-and-deploy Jenkins job to build the Self Managed Commerce deployment package and container images, and use those to deploy or update a full Self Managed Commerce environment suitable for development. For more information, see the Self Managed Commerce CI Pipelines documentation.
The multi-purpose-commerce-tool Jenkins Job
Use the multi-purpose-commerce-tool Jenkins job to build the Self Managed Commerce deployment package and container images, and use those to deploy or update a full Self Managed 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.
The commerce-branch-validation Jenkins Job
Use the commerce-branch-validation Jenkins job to build the Self Managed Commerce deployment package and container images, and use those to temporariliy deploy a Self Managed Commerce environment while automated tests are run against it. For more information, see the Self Managed 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 Self Managed Commerce container 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.