Most modern software today has moved aggressively into using third-party open source dependencies to reduce duplication and accelerate development by using pre-existing code.

Platform operators, you continue to amaze us. You’ve embraced DevOps and site reliability engineering. You’ve applied these philosophies to your daily work. And you’ve used Concourse CI (the “continuous thing-doer”) to address all manner of operational workflows. When we created the project in 2016, we couldn’t have imagined all the ways you’d use Concourse to deliver fantastic stability and scalability outcomes to your stakeholders.

Developers are building and deploying to production with greater frequency. Elite organizations are deploying to production multiple times per day. All the while we continue to distribute our applications even wider with the adoption of micro-services, and global deployments. This consistent churn and increasing code complexity create the perfect storm that makes finding problems even harder. How do you know the changes just committed actually deployed? How do you know the changes worked?

Long release cycles are no longer viable in the world of software development. The promise of DevOps has been to materially shrink time to value. Like most meaningful transitions, this one hasn’t always been a simple flip of a switch. For many organizations, development teams have become complex and unwieldy. So, the custodians of DevOps have found it difficult to achieve broader adoption of DevOps principles across engineering teams.

In the annual roadmap keynote of our SwampUP 2020 conference, JFrog CTO and co-founder Yoav Landman, CPO Dror Bereznitsky and VP of Engineering Avi Cavale delivered a landmark message: If you’re not focused on binaries and distributing them to the edge, you’re risking the future of your business. Under the theme DevOps, Fast Forward, JFrog’s annual user conference showcased how the impact of the global pandemic has accelerated companies’ digital transformation plans.