In this guest post, Ate Douma, Lead Architect at Hippo, Apache member, and committer for the Apache Portals project, discusses how Nexus Professional’s Staging Suite is used to support open source projects such as Apache Jetspeed.
Apache Portals is a collaborative software development project dedicated to providing robust, full-featured, commercial-quality, and freely available Portal-related software on a wide variety of platforms and programming languages. This project is managed in cooperation with a number of people worldwide (both independent and company-affiliated experts), who use the Internet to communicate, plan, and develop Portal software and related documentation.
In addition to managing and maintaining the Maven Central repository, I also serve as the administrator for two very large forge repositories: repository.apache.org and nexus.codehaus.org. This post is going to dive into the details of the best practices that I’ve developed to maintain these very large instances. I will focus on the configuration of Nexus in this post, but if you’re interested in system level details, those are documented here.
Both of these repositories have a few things in common that have driven the design:
- there are many disparate projects deploying artifacts that require fine grained access control per project
- release repositories are synced to central
- they are the most commonly used snapshot repositories in the maven ecosystem
- the majority of users are anonymously reading the snapshots
- they are transitional repositories that replace older static repositories
They also have a few things that are very different:
- Apache is a Solaris Zone
- Codehaus is an Ubuntu Jeos VM
- Apache is using httpd for reverse-proxying and ssl
- Codehaus is using Nginx for reverse-proxying and ssl
This post contains two sections, the first covers some system-wide Nexus configuration, the second contains details about adding individual projects, along with security and staging configuration. If you are setting up a public Maven repository, this post might give you some ideas about configuration and administration issues that you’ll need to think about.
In “A Tale of Two Repository Managers” John Smart compares Nexus to Artifactory, and covers some of the more well known features like Staging and Security. I wanted to emphasize a few more of the other features that are often overlooked.
Most of our users download the tool, install it, and use the most straightforward features: simple proxy repositories, hosted repositories, and repository groups. We’ve gone out of the way to make Nexus intuitive, but I often wonder if enough people know about some of the features offered as part of the base project. Here are some of the features I would have highlighted in any comparison.
Kate Ebneter is a Build Engineer at Ning, Inc. an online platform running the largest number of social networks on the internet. Ebneter is responsible for maintaining mission-critical development infrastructure serving more than 60 developers distributed over seven locations. In this guest post, Kate shares her experience migrating from Artifactory to Nexus Professional. She details the problems Ning encountered with Artifactory, how Ning selected a new repository manager, and what steps they took to migrate from Artifactory to Nexus Professional.
This post from John Smart on the Wakaleo Consulting blog summarizes the results of a preliminary comparison of Nexus and Artifactory. In this post, Smart compares Nexus to Artifactory in the following areas: Installation and General Use, Artifact Searching, Security, Build Promotion Strategies, Deploying Maven Web Sites, and Repository Maintenance.
Here is Smart’s conclusion:
This comparison is far from complete. Both Artifactory and Nexus are solid, feature-rich products, and the competition is good, as it keeps both product teams on their toes. My personal recommendation however goes to Nexus, as in my opinion it has better support for the requirements of larger organisations, and is nicer to work with in the context of build pipeline automation.
To read more comparison and analysis, read Smart’s post on the Wakaleo Consulting blog.