The code we develop ends up being packaged into artifacts that are consumed as dependencies during the development of other software components. We rely on an artifact repository manager, like JFrog Artifactory, to resolve the complex challenges that come with consuming and developing all of these artifacts. Artifactory serves as the foundation for managing binaries in so many organizations, both large and small, as part of an effective CI/CD pipeline.

Go Module vulnerabilities frustrate the lives of many Go developers and can turn a simple project into a battle of endurance between the dev and their patience. With the process of CI/CD shifting left more and more, it’s becoming even more pertinent for developers to be able to track and report vulnerabilities as early as possible. JFrog GoCenter can help track and mitigate vulnerabilities and make the lives of Go developers easier.

JFrog was honored to be recently interviewed by NYSE Floor Talk regarding the company’s efforts during the COVID-19 crisis. The quick video was shot at a safe social distance of course, but focused on JFrog’s FrogCare program. The program provides free software development and DevOps tools to accelerate delivery for research organizations that are supporting the fight against the novel coronavirus.

As a software producer, you need to keep releases moving, even as you need to move your technology ahead. Transitioning your Jenkins continuous integration (CI) pipelines to a newer, optimized system can’t be a roadblock, and your enterprise can’t afford the work stoppage a rip-and-replace rework would require. We understood that deeply when we built our CI/CD solution, JFrog Pipelines.

JFrog CLI now supports autocomplete for both bash and zsh, allowing you to get your work done faster. With this functionality, you can now simply start typing your Bash and zsh commands and the CLI client will provide you with possible options to use. You can scroll through the options using tab. JFrog CLI helps simplify your automation work with the JFrog solutions. For example, using CLI with JFrog Distribution workflows to manage your software releases in a centralized platform.

Starting with Go 1.13, Go modules are the standard package manager in Golang, automatically enabled on installation along with a default GOPROXY. But with other GOPROXY options like JFrog GoCenter, as well as your own Go module packages you need to keep secure from public view, what kind of configuration should you choose? How can you keep your public and private Golang resources from becoming a tangled knot?

You’re digitally transforming yourself and your company in 90 days whether you like it or not. This is the new reality, as you find home office spaces (or lack of them), ways for kids to learn remotely, ways to conduct all of your family gatherings over a Zoom call, and more.

Every company claims to have a cloud/hybrid DevOps platform that enables and powers developers working remotely. Time to make order of the chaos.*

With Google’s new support for Windows containers on Google Kubernetes Engine, you might be eager to start bringing your .NET-compatible Docker workloads to Google Cloud Platform. JFrog is ready to help you hop aboard. In fact, Artifactory’s bags are already packed.

If you’re a Golang developer using Visual Studio Code, keeping at-risk Go Modules out of your apps just got easier, and for free. Today we’re announcing a new version of the JFrog extension for VS Code, available for free download. This integration brings live vulnerability information about every public Go Module you’re using directly into your source editor from the rich metadata of JFrog GoCenter.