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.
The world of software drives digital innovation, and software delivery is increasingly being driven by JFrog. We’re honored and humbled to continue to grow alongside our customers. To enable our next leap ahead, we’re proud to announce that we’ve appointed key industry leaders as independent members of our Board of Directors that will assist us to further grow in the DevOps market.
In agile development, planning, coding, and builds are an ongoing loop. But when a circle is broken, you can’t travel it at full speed. For users of Atlassian Bitbucket Server and Jira, JFrog’s integrations can help Artifactory bridge the gaps for continuous velocity. In a previous blog post, we discussed how to provide Jira information as a critical “why” in your build information.
This blog post will provide you with information on how to use JFrog CLI with JFrog Distribution workflows. JFrog Distribution manages your software releases in a centralized platform. It enables you to securely distribute release bundles to multiple remote locations and update them as new release versions are produced. For those of you who are not yet familiar with the JFrog CLI, it is an easy to use client that simplifies working with JFrog solutions using a simple interface.
One of the exciting things about being a Golang developer today is the strong community that supports the evolution of the language that was developed at Google. The founders of Golang were open to getting engineers involved early-on and the community-centric approach has now become an asset to Go itself.
When software can travel around the globe at the speed of the cloud’s gusts, enterprises need to be extra certain the updates they release are safe for customers to use. If an app built in Palo Alto uses a vulnerable package from Belgrade, losses can ripple from Sheboygan to Shanghai. At JFrog, we believe enabling global DevSecOps in the cloud should be an easy process.
