Are you building and deploying software manually and would like to change that? Are you interested in learning about building a Jenkins pipeline and better understand CI/CD and DevOps at the same time? In this first post, we will go over the fundamentals of how to design pipelines and how to implement them in Jenkins. Automation is the key to eliminating manual tasks and to reducing the number of errors while building, testing and deploying software.

Everyone knows it’s been a tough time for businesses. All flights, conferences and in-person meetings have been canceled. The novel coronavirus (COVID-19) has even made us all stand apart from each other and, if anything, bump elbows only. Times are tough. For those of you in the software business, you know you’ve got it easier than some industries. You CAN work from home. You CAN continue developing. And you should, too.

This is a guest post from Kamesh Pemmaraju of Platform9. As organizations move to a containerized world, whether by producing containerized software, consuming it or both, the need for a managed Kubernetes offering and an Enterprise-tested private Docker registry is apparent. With the introduction of Platform9‘s new Freedom Plan for managed Kubernetes, you can combine it with JFrog Container Registry and power up your containerization transformation for free.

With the release of the JFrog DevOps Platform, we launched the first general availability of JFrog Pipelines, our powerful system for next-generation CI/CD. Pipelines’ many great features help make DevOps pipelines automation rapid, repeatable, and secure. With flexible runtime management, a robust DSL, and a real-time interactive UI, Pipelines is a muscular CI/CD solution we know you’ll love. But what makes Pipelines different?

Today we are announcing the removal of the built-in Docker registry that comes built-in with all Codefresh accounts. The registry will become read-only on April 15, 2020 and we’re aiming to remove it completely May 1, 2020.