Over a million developers have joined DZone.

The DevOps Weekly Report 10/11 – 10/16

DZone 's Guide to

The DevOps Weekly Report 10/11 – 10/16

The leaves are starting to turn. Combine your Dev and Ops leaf piles into a leaf mountain and jump into the best DevOps content from last week.

· DevOps Zone ·
Free Resource

Welcome to the DevOps weekly! Here are the best posts from last week you may have missed: reports from Velocity 2015build tools in Java, an anatomy of the DevOps toolchain, and a post from Dave Farley, who literally wrote the book on Continuous Delivery.

Velocity 2015: Beyond DevOps, Part 1 - John Esposito

Our editor-in-chief John Esposito went to Velocity 2015 in New York last week, and was incredibly impressed by the specificity of the talks. Rather than talking just about how important DevOps or Docker is, sessions have focused more on real user experience and performance, moving beyond DevOps to improve IT even further.  Expect more pieces from John in the future.

Moving From Maven to Gradle in Java - Alex Soto

We’ve been posting a lot of Gradle content in this zone, but we’ve never posted a straight tutorial to install Gradle and use it with Java. Alex Soto’s post is a really great introduction to this fast-growing build tool. 

11 Tools You Must Have in Your DevOps Toolchain - Yaniv Yehuda

DBMaestro contributed a really great infographic that details both the steps of an ideal Continuous Delivery pipeline and what tools will help achieve these goals. It’s a great tool for any organization hoping to adopt DevOps or anyone looking for examples of what tools will help them with a particular step. If anyone on your team needs an introduction to DevOps, this is a good easy place to start.

The Anatomy of an Experimental Organization - Dave Farley

Continuous Delivery co-author Dave Farley wrote a really great piece about what sets truly agile companies apart from those that simply employ agile or DevOps methodologies: experimentation. If you think about it for a little bit, it’s easy to see how companies like Microsoft, Google, and Netflix have succeeded by trying new things without worrying about immediate ROI, knowing that they'll be better for it. Think about where we'd be if Netflix decided it was a waste of time to try to overcome the AWS single point of failure problem, or if Microsoft didn't spend as much on R&D as it does. New or old, it's the experimenters that stand out and succeed. 

devops ,gradle ,java ,culture ,continuous delivery ,velocity

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}