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.

DevOps is a software development practice that combines development and operations teams. When organizations use DevOps, they typically also use agile methodologies for managing and completing projects. The combination of DevOps and agile practices enables teams to build software faster and more efficiently. One of the primary tools of DevOps is the continuous integration/continuous delivery (CI/CD) pipeline.

We now support the upload of Cargo packages to the Cloudsmith platform using the native Cargo publish command.

Thousands of devices means thousands of software components, metadata items, and builds. Coordinating all that data for an Internet of Things system requires a binaries manager built for reliability and scale. That’s the challenge that faced MicroEJ, a software vendor of cost-driven solutions for embedded and IoT devices.

Software development teams are much larger than the engineers that write code. Writing and deploying code are often only the tip of the iceberg. A well oiled software team will often consist of: All of these people need to know something about what the software development lifecycle is producing and shipping, but the level of information can vary dramatically based on a team member's position. Sleuth was built to automatically generate information to satisfy each team member's needs.

Here at Sentry, we use Travis CI, a continuous integration tool for GitHub that lets us automate our tests and view the results right within each pull request. In this blog post, we’ll walk through a quick example of how to automatically create Sentry Releases with Travis CI when a commit is pushed to your project’s master branch. (Sentry Releases enable some of our best features, like identifying the commits that likely introduced new errors, and much more!)

In today’s enterprises, DevOps isn’t one process, but many thinly connected tasks. A stack of DevOps tools that need to work together to operate as a single system, each one requiring its own integration and maintenance. The JFrog DevOps Platform unifies our industry-leading products because DevOps has a single goal: to speed releases from code to production. It takes several tools to build DevOps, but DevOps tools need to function as one.