Dogfooding Nexus

March 16, 2015
By Derek Weeks

1 minute read time

We often share stories about how agile and DevOps teams use Nexus to support their continuous integration and delivery efforts. If you have missed some of these stories, please check out our SlideShare gallery of continuous delivery and DevOps decks authored by development teams from the likes of HP, Adobe, Intuit, Atlassian and Blackboard.

There are many stories from the development community. Here's a small sample of the stories we recently highlighted:

DevOps Best Practice - Establishing a Single Source of Truth (Reedy Feggins at IBM).
Integrating Jenkins, SonarQube, and Nexus (Michael Rumpf at InfoSupport).
Chaikin Analytics- A DevOps Perspective (Boxupp).
Publishing artefacts to Nexus using SBT and Travis CI (Jan Machacek at Cake Solution).

But how does Sonatype use Nexus to support our development efforts? Well, our development team is about to tell you. In fact, they plan to give a virtual tour of our factory floor (e.g., tool chain) while discussing their own best practices for agile software development across a geographically distributed team.

They will also spend time discussing their use of Nexus, Bamboo, Jira, HipChat, AWS, Ansible and other solutions to streamline our development efforts, improve the quality of our builds while reducing rework, and speed time to market for new releases. If you would like to join them for the virtual factory tour, you can sign up here. Your questions are encouraged throughout the tour.

If Nexus is part of your continuous delivery efforts, we encourage you to share your experience, just as others have done. We'll then do our part to help spread the word on your story within the Nexus community.

Written by Derek Weeks

Derek serves as vice president and DevOps advocate at Sonatype and is the co-founder of All Day DevOps, an online community of 65,000 IT professionals.