Building the Deployment Package · CloudOps for Kubernetes

Build Commerce Deployment Package

After you have access to the Jenkins server and the bootstrap and build-jenkins-agents jobs are complete, you can start building the deployment package. For information, see the How to Access Jenkins section.

The build-deployment-package job in Jenkins requires the following parameters:

cloudOpsForKubernetesRepoURL: The Git repository URL of the CloudOps for Kubernetes code, used for the Jenkinsfile for this build
cloudOpsForKubernetesBranch: The branch of CloudOps for Kubernetes to use for the Jenkinsfile
epCommerceRepoURL: The Git repository URL for the Self Managed Commerce code
epCommerceBranch: The branch of Self Managed Commerce to use
epCommerceCredentialId: The Jenkins credential ID used to access the Git repositories

note

The values set in the docker-compose.yml file during the bootstrap process are the default values.

The job pushes the deployment package into the Nexus server, which is setup during the bootstrap process, in the ep-releases repository at com.elasticpath.extensions.ext-deployment-package.

The job also creates an artifact named output.json. This file contains values you need to find the deployment package when you are building the container images.

tip

Enable the new Eclipse P2 Caching Proxy to improve build stability.

Commerce Manager builds rely on external Eclipse P2 repositories. The Jenkins Maven build process typically downloads the Eclipse artifacts from the Internet on each run and, if the remote Eclipse servers are having issues, downloads might fail or time out. Enabling the Eclipse P2 Proxy allows you to reduce the repeated external Eclipse downloads. For more information, see Eclipse P2 Caching Proxy.

Next Steps

With a deployment package built, continue on to building the Commerce container images.