Build Commerce Deployment Package
After you have access to the Jenkins server and the
build-jenkins-agents jobs are complete, you can start building the deployment package. For information, see the How to Access Jenkins section.
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 Elastic Path Commerce code
epCommerceBranch: The branch of Elastic Path Commerce to use
epCommerceCredentialId: The Jenkins credential ID used to access the Git repositories
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
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 Docker images.
With a deployment package built, continue on to building the Commerce Docker images.