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?
Red Hat OpenShift and JFrog Artifactory are a smooth fit together for cloud native, containerized software development at enterprise scale. With the new availability of OpenShift operators certified for JFrog Enterprise, that fit now fastens tight.
My name is Kat Cosgrove, and I’m a Developer Advocate at JFrog. Before that, I was an engineer on JFrog’s IoT team. Our goal is to bring DevOps to the edge, because it shouldn’t be as difficult to update these kinds of devices as it currently is. In pursuit of this goal, we found a lot of interesting solutions that we could bring into a CI/CD pipeline for embedded Linux devices, and eventually built a rather flashy proof of concept that put several of these solutions on display.
We work best by coming together. That’s why we built the JFrog DevOps Platform, bringing together our set of solutions to operate as a single, unified user experience. That unity powered by Artifactory 7 helps bring total understanding and control of your software build pipelines. To keep it running, you also need a unified, real-time view of the entire platform’s operation.
A friend that can’t keep a secret isn’t one you’ll rely on. The same is true for your mission critical CI/CD tool that you have to entrust with credentials for each integrated component. Keeping your secrets safe can be a challenge for CI/CD tools, since they need to connect to such a variety of other services. Each one needs its own password or token that must be kept hidden from prying eyes.
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.
In this webinar you will learn:
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.
