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.
Some things, like high-end coffee or enterprise technology, are worth working and waiting for. But if you can get quality without the effort or delay, wouldn’t you? Installing or updating a self-managed (BYOL), High Availability edition of JFrog Artifactory hosted in an Azure VM can be a complex, and time-consuming process.
In times of crisis and challenge, the best in humanity comes out. We all want to help, we all want to pitch in and we all desire safety and health for our loved ones and communities. And we ideally want to assist genuinely – in a way that helps others without strings attached. JFrog is no different.
As continuous software deployments grow and become the accepted standard, security measures gain even more importance. From development and all the way through to production, security requirements should be adopted by all teams in an organization. JFrog IDE integrations provide security and compliance intelligence to the developer right from within their IDE.
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.
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.
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!
Everyone knows it’s been a tough time for businesses. All flights, conferences and in-person meetings have been canceled. The novel coronavirus (COVID-19) has even made us all stand apart from each other and, if anything, bump elbows only. Times are tough. For those of you in the software business, you know you’ve got it easier than some industries. You CAN work from home. You CAN continue developing. And you should, too.
This is a guest post from Kamesh Pemmaraju of Platform9. As organizations move to a containerized world, whether by producing containerized software, consuming it or both, the need for a managed Kubernetes offering and an Enterprise-tested private Docker registry is apparent. With the introduction of Platform9‘s new Freedom Plan for managed Kubernetes, you can combine it with JFrog Container Registry and power up your containerization transformation for free.
