<iframe src="//www.googletagmanager.com/ns.html?id=GTM-TT8R4P" height="0" width="0" style="display:none;visibility:hidden">

Sonatype Blog

Stay updated on the latest news from the makers of Nexus

They Sent 300 Employees to a DevOps Conference

Last year, I was able to attend 18 DevOps conferences. I saw some awesome presentations, met incredible people, and expanded my knowledge of the latest practices. While my role as the DevOps Advocate for Sonatype enables me to get out to all of these conferences, not everyone has the time, the budget, or the approval to get to even one event a year.

Nexus 3.3 Delivers Free Next-Gen Repository Health Check and Git LFS Support

Sonatype is excited to announce the immediate availability of Nexus Repository 3.3 in OSS and Pro editions.  What’s in this latest release?  We’re glad you asked:

 

Next-Generation Repository Health Check

We first introduced Repository Health Check (RHC) in 2012.  Now, every day we analyze over 80,000 repositories and 50 million components for our Nexus users.

Set up your own Continuous Delivery Stack

Last week I wanted to try new things with ‘pipeline as code’ with Jenkins. The best way to try new things is running it as Docker containers. This way I can keep my MacBook clean and don’t mess up existing stuff I am working on (also see this article about what Docker can offer for a developer). Another big advantage by using Docker is that there is already a complete stack of Dockers available to set up the necessary tools. However, for some unclear reason this stack didn’t work on my MacBook (see this issue) so I took this opportunity to build my own stack with some Dockers of my own choice :-).
The tools in my stack are:

CI/CD with OpenShift

Achieving CI/CD with Kubernetes

Hola amigos !!(In English – Hello Friends !!) Hope you are having a jolly good day ! Continuous Integration/Delivery is best said in terms of Martin Fowler, according to him it can be defined as, “Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.”

DevOps for Small Organizations: Lessons from Ed

Ed was demoralized. He had just heard a speaker who would change his life. He knew he needed to change, and he knew what the end goal was. He just didn’t know how to get there. He needed fresh air. He needed endorphins. What better way to do that than go on a 6-hour run through some of the seedier neighborhoods of Vegas to the edge of the desert.

DevOps Confessions from Fannie Mae, Liberty Mutual, and Capital One

True Story.  Over the past few years, Fannie Mae transformed the way in which they delivered software.  Deploys increased from 1,200/month to 15,000/month.  At the same time, productivity increased by 28% while reducing costs by 30%.  But, how did they do it?