Collaboration is the Key to Scaling Development

March 30, 2017

By Kit Merker

SHARE:

When you’re building a DevOps environment, no single tool will solve all your problems. There is no magic silver bullet to streamlining your engineering team and shipping faster. There are many pieces that need to work together seamlessly to create a repeatable system for releasing high quality, high value software to customers.

In fact, the “magic” behind DevOps is that it reduces the overall communication load between developers. What used to be handled in meetings moves to APIs, what happened in QA moves to continuous integration, and manual security reviews move to automated scanning. Re-inventing the wheel has moved to open source and public pull requests.

The reason we can ship faster is because we now can let software help us build software; that’s the true essence of DevOps.

So of course, your DevOps tools need to work together! JFrog has longstanding integrations with some of the most important infrastructure – household names like Jenkins, GitHub, and Docker to name but a few. I wanted to share some new integrations expanding our universe to make DevOps available to all.

Microsoft Azure – Our Software-as-a-Service version of Artifactory Pro & Enterprise is now available on Microsoft Azure in addition to our existing cloud hosting options. Artifactory SaaS is highly available and kept up-to-date with new versions of Artifactory. When you’re optimizing your flow from developer to production, putting everything – CI system, binaries, tests, and production systems – in one cloud means releasing faster. Now we give you the choice to align your binaries and artifacts with your all workloads on Microsoft Azure.

Chef – Artifactory 5 now supports Chef Cookbooks as a native package type. Your Infrastructure-as-Code artifacts deserve their own lifecycle outside of source control. Think about it – you don’t code and test them the same way as all your components, but you store them in Git? Now you can treat Chef Cookbooks the way you would any other artifact that can be separately versioned, tested, promoted, and released along with your build in Artifactory.

Puppet – Artifactory 5 also supports Puppet Modules and will let you run your own Forge repository behind the firewall or in the cloud as a private repository. Again, infrastructure-as-code belongs in its own lifecycle and your tools should just work. That’s why we’ve updated the Puppet client to support Artifactory Puppet repositories.

I joined JFrog last summer to grow our collaborations and we are just beginning to work closely with a number of players. Our goal is to help software development organizations deliver value to end customers faster, and all of our partnerships begin with this goal. Please stay tuned as we continue to do the hard work of making our tools work with the constantly shifting world of DevOps tools.