Go modules have helped bring order to Go development, but there’s been some disorder lurking. Managing module pseudo-versions can be difficult, especially with some of the latest changes to Go. JFrog GoCenter, the free repository of versioned Go modules, now includes some important updates that can help you stay on course. Let’s take a look at how pseudo-versions work, and what you can expect from those changes.

Kubernetes offers scalability and reliability for your container-based applications. Combine this with GKE, and you now eliminate the need to install or operate clusters on your own. A huge plus to using GKE is that you now will be running Kubernetes in a GCP environment, therefore you can utilize all the handy integrations Google has to offer. Codefresh simplifies the process even more, by automating the process of getting your code built, tested, and deployed.

There are many reasons why you may want to use Artifactory as your Maven repository. For example, it allows tagging Maven artifacts with custom properties, so that they can later be found based on specific criteria. It stores build metadata about your artifacts, and allows controlling the repositories used by the Maven build, without modifying the pom file. In this post, I’d like to focus on one specific advantage, Maven deployments in Jenkins.

In our previous announcement for the removal of the Codefresh Docker registry, we presented a timeline of the migration phases along with the actions expected from our customers. One of the milestones in the migration process is the introduction of our new Image API along with several enhancements on the pipeline build step. We believe that these features deserve a dedicated explanation of why they are useful on their own (regardless of the registry removal).

This is a repost from the JFrog dev.io blog site. When you’re new to an industry, you encounter a lot of new concepts. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers. In this series, I’ll cover tools and terminology common to the DevOps space, plus the occasional newbie-friendly tutorial for emerging or established technologies. If you have a request or suggestion, let me know!

As a team that does pure serverless, we place a lot of emphasis on fast deployments. Lately, though, as our codebase has gotten larger, and the number of interactions between the microservices has increased, we have come up against the classic problem of excessively long test execution times in our serverless continuous integration.

Today, we’re excited to announce you can now integrate LaunchDarkly with Sleuth, allowing you to track feature flags as a source of change in your DevOps stack. The Integration LaunchDarkly gives developers fine-grained control over which users see which features, and with our native LaunchDarkly integration you can now track the status and impact of feature flags relative to other source changes in your projects, such as code, issues, etc.