Manage Nexus Artifacts
After deploying CloudOps for Kubernetes, a Nexus server is created and used to cache artifacts from external Maven repositories and store Elastic Path artifacts. Jenkins jobs create these Elastic Path artifacts, and you must periodically clean up to maintain sufficient disk space in Nexus.
Out of the box, the Nexus server comes with tasks and Jenkins jobs that clean up artifacts in the Elastic Path Snapshots and Elastic Path Releases Nexus repositories. Find these tasks in the Administration section under Scheduled Tasks in the Nexus web UI.
The EP Snapshots Repository
Two tasks in the Nexus server delete artifacts from the Elastic Path Snapshots repository called Remove unused snapshots from EP Snapshots repo and Empty trash from EP Snapshots. These tasks run hourly and clean up any artifacts in the repository over a day old.
The EP Releases Repository
Two tasks in the Nexus server delete artifacts from the EP Releases repository called Cleanup EP-Release Artifacts and Empty trash from EP Releases. These tasks are triggered to run hourly by the Jenkins job cleanup-release-artifacts and cleans up all artifacts in the repository.
To prevent this job from deleting artifacts used during a maven build; the job fails if the following Jenkins jobs are in the Jenkins build queue or are already running:
build-deployment-packagerun-cortex-system-testsrun-recursive-commerce-testsrun-select-commerce-testsmulti-purpose-commerce-toolbranch-validation-pipelinecommerce-test-and-deploy
Parameters for the cleanup-release-artifact Jenkins Job
cloudOpsForKubernetesRepoURL
The URL to your hosted copy of the cloudops-for-kubernetes Git repository.
cloudOpsForKubernetesBranch
The branch of the cloudops-for-kubernetes Git repository to use during the deployment.