On July 15th the Codefresh registry that is part of all Codefresh accounts will be removed from service. The removal is part of a big round of improvements to our native integration with Docker registries. We have invested significant efforts in using Codefresh as a unified platform for Docker images and the way they are used inside CI/CD pipelines. More details on the migration actions for the Codefresh registry can be found in our timeline announcement.

Cloudsmith can help reduce the amount of resources you need to devote to package management and DevOps, whilst delivering a better service to your teams than ever before. Here’s how and why. Package management is right at the heart of DevOps. Packages are both inputs and outputs in the DevOps process, and indeed many individual packages are both. Effectively, packages are the currency that engineers work in.

Installing Artifactory on GKE, or on any Kubernetes cluster for that matter, can be complex. You have to think through several scenarios, switch back and forth between UI and command line, create a lengthy Helm command, search for acceptable parameters … and so on. All this before you have to configure certificates, licenses, database settings, node settings. But there’s more, what about future proofing it?

Red Hat OpenShift and JFrog Artifactory are a smooth fit together for cloud native, containerized software development at enterprise scale. With the new availability of OpenShift operators certified for JFrog Enterprise, that fit now fastens tight.

DevOps is an approach to software development and delivery that emphasizes collaboration between different stakeholders. DevOps also places priority on automation and the integration of different tools in a single, well-oiled pipeline. Ultimately, DevOps boils down to cultural values and goals. When it comes to tooling and processes, there is no one right way to “do” DevOps; a variety of different approaches are possible.

My name is Kat Cosgrove, and I’m a Developer Advocate at JFrog. Before that, I was an engineer on JFrog’s IoT team. Our goal is to bring DevOps to the edge, because it shouldn’t be as difficult to update these kinds of devices as it currently is. In pursuit of this goal, we found a lot of interesting solutions that we could bring into a CI/CD pipeline for embedded Linux devices, and eventually built a rather flashy proof of concept that put several of these solutions on display.

Software Engineering is hard. As time has progressed, the number of languages, frameworks and packages available has grown to the point where it’s rare nowadays to find a project that is developed entirely in a single language or within a single ecosystem. A typical project uses the best languages and frameworks for the job, and these frequently differ depending on what part of the project is being developed.

We work best by coming together. That’s why we built the JFrog DevOps Platform, bringing together our set of solutions to operate as a single, unified user experience. That unity powered by Artifactory 7 helps bring total understanding and control of your software build pipelines. To keep it running, you also need a unified, real-time view of the entire platform’s operation.

The summary: Cloudsmith provides a way for vendors to sell, license and distribute software as packages. To any customer, anywhere in the world, across a reliable and performant infrastructure, and handling all licensing and invoicing / billing challenges. As most of the readership of this blog will know, a huge proportion of the software developed around the world is dependent upon the third-party packages and libraries we integrate into our projects.

A friend that can’t keep a secret isn’t one you’ll rely on. The same is true for your mission critical CI/CD tool that you have to entrust with credentials for each integrated component. Keeping your secrets safe can be a challenge for CI/CD tools, since they need to connect to such a variety of other services. Each one needs its own password or token that must be kept hidden from prying eyes.