mobile.de, a subsidiary of eBay, Inc., is an online marketplace where buyers can find new and used cars as well as motorcycles, trucks and motorhomes. The company’s services are aimed at professional car dealers and private customers in Germany. Two-thirds of all car dealers registered in Germany use the Internet vehicle marketplace provided by mobile.de.
The DevOps, Release and Build Team provides services and solutions to the whole of eBay Classifieds, which manages local classifieds in regions around the world. The team’s main initiative is to boost collaboration and faster delivery for the product development teams and site operation teams. Nexus Repository is utilized as part of the CI/CD pipeline to provide a consistent, secure environment across all development environments.
The DevOps, Release and Build Team of seven engineers at mobile.de are responsible for providing secure CI/CD pipeline solutions for multiple teams. They also manage the use of reporting tools such as Atlassian Confluence and JIRA.
“We are serving several teams inside eBay classified and would like to create consistency across the teams,” explained Donato Emma, Team Lead of Engineering Support. Before the CI/CD pipeline was implemented, infrastructure was managed manually. There was no centralized storage for multiple binary types, making it virtually impossible to track open source component usage.
Any pipeline solution would have to accommodate multiple groups and projects, while providing security within that pipeline.
mobile.de concentrated their consistency efforts on the creation of a CI/CD pipeline. For integrated security, mobile.de uses Nexus Repository as a local, private repository integrated with tools such as SonarQube, Selenium Grid, OpenStack, Jenkins and Ansible.
“Nexus Repository is a key part of the CI/CD pipeline for several of the platforms inside Mobile.de,” says Donato Emma. “We are using the Nexus Repository to store artifacts. Since the introduction of Nexus 3, we have begun to use it for different types of artifacts such as Bower, PyPi and other formats. We are also using this repository to store binaries being used in the build process and to proxy outside of the repository. A single Nexus instance is capable of handling quite a large amount of data."
Docker containers are a key part of the pipeline. “Nexus 3 is used for the Docker registry functionality,” Emma explained. “We have not found the need to write plugins because the functionality offered by Nexus is more than adequate for what we’re doing.”
The use of Nexus Repository as a centralized storage for multiple binary types has created a consistent, secure environment across multiple teams. Two hundred software engineers in multiple groups at mobile.de are now getting the benefits of the Nexus platform.
There is a consistent development environment, with surprisingly little need for support.
“We were having a little trouble on our side on how to configure a specific type of security for the Nexus Repository. We wrote a support ticket to Sonatype, not expecting much of a response based upon our experience with other companies. We were really surprised at how fast we got an answer back from the support team at Sonatype,” explains Emma. “We received a reply within the same day and were able to sort out the issue. It was unexpected, to be honest. There was no need for escalation of the issue. It was quite a nice experience.”
Donato Emma and mobile.de are happy with the outcome of the CI/CD pipeline, and the role Nexus Repository plays.
“I would recommend Nexus as a platform. There is very low effort to operate it and gain value from it. Once Nexus was running, we hardly had to touch it. Even with the new implementation of Nexus 3, it’s up, it’s working and it’s creating a lot of benefit for the teams using it. We’ve had a single Nexus instance standing up for two years. The maintenance and support effort is zero because everything just works.”