Introduction One of the SRE team’s goals at Moogsoft is to make sure our feature teams have an easy path from local code changes to production. Changes rolling out to production mean new features, bug fixes, optimizations, and more, which translates into value added for our customers. In short, at Moogsoft we are all about making sure our product is continually evolving, and one way the SRE group helps is by building shared Jenkins functionality our engineers understand and can use quickly.

JFrog is pleased to announce that our comprehensive Cloud Enterprise+ plan is now available on Amazon Web Services (AWS) Marketplace through Private Offers. JFrog Cloud Enterprise+ on AWS is a universal, highly-available SaaS offering of the JFrog Platform for demanding DevSecOps at global scale.

Continuous integration is the first half of the acronym CI/CD, with Continuous Delivery completing the second half. In this three-part article, we look at the two halves of CI/CD to define and understand them, and then, in part three, we talk about how Uptrends fits into your CI/CD processes. Let’s get started at the beginning with continuous integration.

With a near-endless list of Go Modules, it can be overwhelming trying to decide which is best for your Go build. For new Go developers, it can be difficult to pick a winner for your specific use case. This phenomenon is nothing new. In fact, it’s one of the reasons why open-source is so important for developers. Oftentimes, when a module is published by a developer, it was likely developed to solve a specific problem that they are facing.

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?