Staying Universal with Shippable CI/CD

JFrog, Shippable, SwampUP and Everything in Between

By Baruch Sadogursky, Head of Developer Relations May 9, 2019

5 min read

You probably heard about the latest JFrog Shippable acquisition, and may have some questions. These may include, but are not limited to, “Will I have to use Shippable now?”, “Will JFrog stop supporting other CI solutions?”, “Can I still use Shippable now?”, “What’s this JFrog thing?!”, “What’s this Shippable thing?!”, “What’s up with the frog naming, I mean, a conference named swampUP, really?!”, “When will there be world peace?”, and… other important questions. I was wondering about a lot of those when I went to sit with the right people to find the answers.

Important Disclaimer: The post and the video contain no Avengers Endgame or Game of Thrones spoilers.

Here’s a quick summary of what Avi Cavale (Sr. Director R&D; formerly co-Founder and CEO of Shippable) and Ido Green (VP of Technology) had the chance to talk about.

What is Shippable and how does it work?

Shippable is a CI/CD platform that enables flexible DevOps workflows. From simple to complex pipelines, it translates DevOps workflows into steps in your pipeline, such as: build, package, push, promote, distribute and deploy.

Why did JFrog Acquire Shippable?

Focusing on customer needs, Shippable enhances the user’s productivity by completing the DevOps pipeline automation. The developer-to-runtime diagram below shows how with Shippable’s CI and CD capabilities, JFrog now provides a holistic solution. Spanning all the way from the second you commit your code to Git (or other source control), through to where the software is installed on runtime. This can be container runtime, such as Kubernetes, an end user device such as a laptop or smartphone, or an IoT device such as Raspberry Pie mounted on a donkey-car or real self-updated car.

Integrated? Yes. Universal? You bet.

Everything, from Git–to-K8S can be powered by JFrog. Click To Tweet Choose the JFrog components that work for you, and they will integrate perfectly with all the other players in the ecosystem.

What are the plans for the day-to-day user experience?

Shippable is built with an “everything as code” concept and with a developer first mindset. The upcoming launch at swampUP, JFrog’s annual DevOps conference, will include new UI builders and startup templates for the most frequently designed pipelines. These will be available to you right out of the box, and can be further customized using the DSL or a new web builder.

What about being universal?

More specifically, the big question is: with an in-house CI/CD tool, how will this change JFrog’s approach of being universal and open?

Shippable will enhance and improve the current state. This means that JFrog will continue to support the radically universal concept, supporting you as you continue to use the tools that work best for you. Shippable is built with the same concept of universality, extending and completing the puzzle rather than replacing everything you’ve already done. As said by Avi Cavale:

“We’re really not trying to get people to reinvent things that they’ve actually already done. If it’s not broken, you shouldn’t try to go fix it. That’s where we started Shippable. We have adapters to Jenkins, we have adapters to CircleCI or any of the popular tools so that our whole idea is to extend and give you the capabilities that you might not already have but you’re actually doing.”

What is swampUP and what does it have to do with anything?

Next month, June 17-19, JFrog is hosting swampUP, its annual user conference. What does this have to do with you? This is your opportunity to get more information about JFrog+Shippable from those who made it happen and those who are working on the integration! Both Avi and Ido, together with the rest of JFrog technical leadership will be there and will be more than happy to answer all your questions (maybe except the world peace one).

Also, as a thank you for reading this blog post and watching the video, here’s a little treat from JFrog:

To summarize…

JFrog users will continue to have the freedom of choice to choose whatever works best for them. They will have better metadata, better visibility, better control. If they lack knowledge or implementation in some parts of their pipeline, they will be able to use the out of the box solutions that JFrog provides.

Here’s the full video: