Software is more than building code. Developing software and ensuring quality builds requires managing a complete software supply chain. With the many security threats across the supply chain, managing each and every aspect of the software you deliver to your customers, including the entire process of how it was made, is critical to your organization. This means setting up your software release cycle to include DevOps and security best practices.

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.