230

Sonatype-Nexus cleanup — Advanced level

At travel audience we run a microservice-based system on top of Kubernetes clusters. Since Kubernetes pods are working with docker images, changes to our services are built into docker images and pushed to an artifact repository.

travel audience’s Nexus is primarily filled with docker images.When changes are made to our git repositories our extensive CI pipeline is triggered, part of which is building a docker image. That means that any commit in our git repositories will be built and tagged with the change name (ie. SHA code, branch name, PR number or git tag). All these artifacts are then pushed to Nexus to allow our K8s clusters to pull them when needed.

This setup of pushing to Nexus on any change was created in order to allow our developers to test their work. With this approach, they are able to test independently and in integration with other services in our non-production environments.

This build logic can cause clutter. Not only did it cause the persistent volume of Nexus to reach its capacity, but also made Nexus backup process extremely long. Moreover, navigation through the extremely long list of Docker tags in Nexus started to be troublesome.

Click here to read.

Share:

Related articles

About travel audience

We provide integrated data-driven solutions for travel advertising and connect destinations and travel brands with potential travelers at scale.
Learn more