Operations | Monitoring | ITSM | DevOps | Cloud

Continuous delivery is a software development approach in which code changes are automatically staged for production release. A foundation for modern application development, continuous delivery extends continuous integration by automatically deploying code changes to test and production environments after the build phase. When properly implemented, developers have deployable build artifacts that have passed a standardized testing process and can be deployed to environments as needed.

One of the game changers in modern software development is Continuous Integration and Continuous Development (CI/CD). Both large, established organizations and small, growing companies use CI/CD to deliver software faster and to detect bugs in the software lifecycle. In this tutorial, I’ll create a full pipeline to practice CI/CD using Jenkins, including how to set up Jenkins on Docker. I’ll give an in-depth view of a Jenkins pipeline example using Jenkinsfile.

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.

Continuous integration and continuous delivery/deployment (CI/CD) pipelines are integral to software development and management nowadays, yet there seems to be a lot of confusion about what CI/CD actually is. In this article, learn about the definitions and explanations of CI/CD, the difference between CI and CD—and the difference between CI/CD and DevOps.

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.

State of DevOps moderator Ciara Carey recaps the Dec 15 session.