For companies to survive until 2022, they’ll need to focus on two things: Binaries and Edges. We’ve just wrapped up swampUP 2020, where we showcased this bold idea. We heard from you firsthand how DevOps Fast Forward is a must, and how software must be able to be distributed anywhere to enable the continuity of any business. Your experience confirmed how the global crisis has accelerated the digital transformation in your companies.

Today we’re announcing a new round of funding that brings an additional $27M to help us invest in growing and building Codefresh. When we started, we wanted to revolutionize the way people build and deploy software with continuous integration and delivery. I’m proud to say that we were the first platform to see the game-changing value of containers and Kubernetes.

This blog is part of our series on how to use Atlassian features, automations, and integrations to take time back to ship better code, faster. Click here for the full list of 12+ new features or follow us on Twitter to stay up-to-date! Picture this: you've landed in a Development team that practices DevOps religiously (or maybe you're even leading one!). But despite spending hours integrating your tools and reading your edition of the Phoenix Project, you still feel like there's something missing.

Machine Learning (and deep learning) applications are quickly gaining in popularity, but keeping the process agile by continuously improving it is getting more and more complex. There are many reasons for this, but primarily, behaviors are complex and difficult to anticipate, making them resistant to proper testing, harder to explain, and thus not easy to improve.

Since the inception of JFrog – with OSS Artifactory – we’ve been adamant that you simply cannot deliver software with any type of scale, speed, or reliability without a robust artifact management solution. Now, over a decade later, other vendors in the industry are finally starting to catch on. AWS recently announced its CodeArtifact service for binary management.

At Cloudsmith, we pride ourselves in being the central source of truth for your packages and build artifacts. We provide one global platform to centralize your assets and give you the control and visibility that you need as part of a modern DevOps process.

Ansible has become one of the most popular tools used by operations teams to automate their IT tasks. It allows them to quickly, and at the largest enterprise scale, manage the configuration of their IT systems. This includes software and infrastructure on-premise and in the cloud. Its open-source roots has allowed it to grow a large global community with an equally expansive ecosystem of integrations.

The number of publicly available Helm charts is continuously growing and while this is great for the community, it can be challenging to navigate the vast sea of Helm charts and Helm chart repositories. Like a ship’s captain, you need more than just a list of where you can go, but the details to ensure those under your charge arrive certainly and safely. Not just what can be seen on the surface, but what lies underneath, and the hazards that await.

If you’ve been following along, the last two articles explained the CI/CD (Continuous Integration/Continuous Delivery) processes. In this article, we look at how Uptrends fits into those processes. Uptrends can fit into your CI/CD process in several different ways. For example, you may want to use Uptrends for the testing and monitoring portions, include your monitor updates as part of your automation processes, or both.

Building a healthy productive engineering culture is hard and just deploying frequently with continuous deployment is not enough. I'm going to show you how you can use a carrot, not a stick, approach to take continuous deployment to the next level by celebrating team values with Sleuth.