We all know that artifact management is an important part of our development lifecycle, and if youโre using Jenkins youโll also need to store your builds and binaries. In the world of DevOps, efficient integration and management of artifacts and dependencies are crucial for successful software delivery. Together, Jenkins and JFrog Artifactory offer a powerful โฆ
TL;DR In part one of this series, we looked at what is a dependency, different types of dependencies, and their benefits in our code. In part two, weโll look at the risks of using dependencies. Whenever we add a dependency we are increasing the risks of any software development cycle. What can possibly go wrong? โฆ
TL;DR We use software dependencies as part of our ongoing daily work. In part one of this series, weโll take a look into what dependencies are, why we use them and the tools we can use to manage them and gain trust in our software supply chain. Software Dependencies Dependencies are artifacts that enable applications โฆ
The path between two clouds ought to be a speedy two-way street. Thatโs the DevOps pipeline principle behind the JFrog Artifactory App for Jira, which forges a traceable link between your issues in Jira Cloud and your builds in Artifactory on the JFrog DevOps Platform for cloud. Bringing Issue Tracking to your DevOps Pipeline Once โฆ
โForewarned is forearmed,โ cautions the old proverb, and that truth coined in the 16th century is even more apt for DevSecOps in the 21st. The earlier you know about vulnerabilities, the better you can avoid making them part of your software. Thatโs the same principle behind a โShift Leftโ DevSecOps strategy. Rather than waiting for โฆ
