Full automation makes your Continuous Deployment (CD) faster, seamless and less error prone. For example, triggering the deployment of your Helm Chart when a Docker image is pushed to production. The latest JFrog Artifactory release makes this easy! With a new Custom Webhook feature that enables a direct integration with a variety of services such as Gitlab Pipelines, Jenkins and GitHub Actions.

Our modern life depends on software from the most trivial to critical task. How software is built, behaves and what actually contains are fundamental questions that almost all stakeholders of the Software Development Life Cycle need to know. Being able to effectively manage your binaries (aka software packages, artifacts, containers, images…) provides full control over your binary lifecycle.

As software development becomes more complex, it’s important for IT and software leaders to stay up-to-date on the latest trends. Tools like Stack Overflow’s Developer Survey and the Tiobe Index can be helpful, but they rely on indirect data and don’t provide a full picture of what’s actually being used in production. JFrog’s Software Artifact State of the Union is different.

Yesterday, GitHub changed how the archives they provided are made. The result of this change surprised developers, triggering pipeline failures all over the world in most ecosystems. According to this GitHub post, this is a consequence of recent changes to Git itself, released almost six months ago and just deployed within GitHub now with unforeseen impact. This change has thankfully been retracted.

As businesses strive to keep up with the speed of digital transformation, they’re turning to DevOps practices to help them automate the delivery of code changes. In a world where delivering secure quality software updates fast-drives business value, enter the JFrog Cloud DevOps Platform. The JFrog Platform unifies, accelerates, and secures your software delivery, from development to distribution.

The modern software supply chain is complex. JFrog internal data shows that most enterprises use 12+ package types and 90 percent of applications depend on open source software. Additionally, there is a wide array of tools to support the software development process, including Source Code Managers (SCMs), Integrated Development Environments (IDEs), CI/CD suites, and more. But managing the diverse activities associated with the software supply chain with separately administered tools can be tricky.

After two years of virtual and reduced-size events, AWS re:Invent was in full swing for 2022 with over 50,000 attendees — more than double 2021’s in-person attendance. Among the many new service and feature announcements, there were two themes that resonated (re:Sonated?): event-driven architectures and cloud-powered innovation. These uniquely position AWS partners to accelerate their customers’ business transformations.

As software becomes increasingly complex, the need to secure the software supply chain becomes more important — and more difficult. But how can businesses address the challenges of securing their software supply chain? The International Data Corporation (IDC) offers critical insight.

As macroeconomic pressures increase, it’s common to hear more in corporate hallways about “Tail Spend.” But what is it, and how can companies move this sometimes-shadowy expenditure into a strategic advantage for IT and DevOps teams? TOC: Here are some answers to commonly asked questions.

Why should you keep Terraform module, provider, and backend registries in a binary repository manager like Artifactory? Because, like your builds, packages, and other artifacts, your Terraform files are a key part of your software supply chain. Terraform is a widely used open source infrastructure-as-code (IaC) software tool to manage the entire lifecycle of cloud service infrastructure.