Turn any signal into insight and action. See how PagerDuty Digital Operations Management Platform integrates machine data and human intelligence to improve visibility and agility across organizations.
Connect insights to real-time action by aligning teams through the shared language of business impact.
Check out the latest products we’ve been working on—including event intelligence, machine learning, response automation, on-call, analytics, operations health management, integrations, and more.
Digital Operations Management arms organizations with the insights needed to turn data into opportunity across every operational use case, from DevOps, ITOps, Security, Support, and beyond.
Over 300 Integrations
Discover DevOps best practices with our library of webinars, whitepapers, reports, and much more.
Learn best practices and get support help with resources from our award-winning support team.
See how PagerDuty works with our live product demo — twice a week, every week.
We've created a maturity model to assist on the journey to digital operations excellence. Take our short assessment to find out where your team falls!
Interactive, simple-to-use API and technical documentation enables users to easily try updates and extend PagerDuty.
Engage with users and PagerDuty experts from our global community of 200k+ users. Become a member, connect, and share insights for success.
Get all your PagerDuty-related questions answered by exploring our in-depth support documentation and community forums.
In The Hitchhiker’s Guide to the Galaxy, a group of scientist mice built a mega-computer named “Deep Thought” to Answer “The Ultimate Question of Life...
PagerDuty helps organizations transform their digital operations. Learn more about PagerDuty's mission and what we do.
Meet our experienced and passionate executive team.
We are risk-taking innovators dedicated to delivering amazing products and delighting customers. Join us and do the best work of your career.
With the PagerDuty Foundation, we are committed to doing our part in giving back to the community.
This is one of two PagerDuty posts on Continuous. Check out our second one: Continuous — Build, Break, and Fix Fast
There is a large gap between the understanding of modern processes and technologies, and actually doing something with them. In the DevOps movement, many of the core functions have met wide adoption, such as orchestration, release automation, and analytics. But what have not been as widely adopted are the end-to-end processes of continuous delivery and deployment, which is not a case of understanding — It is dictated by existing organizational elements and practicality. Are you ready for continuous delivery and deployment?
There is a deficit in the definitions of continuous delivery and continuous deployment. So before I dive deeper into the topic, I need to give my definition. Delivery means up to release, but not direct to production. There is still a gate, and someone has to hit the Go button. Deployment refers to what is put directly into production after all tests pass. The difference might seem trivial, but it isn’t. Deployment not only allows but also requires releases on a daily basis. It also implies a very robust reverting mechanism, which is heavily reliant on great alerting and log analysis.
The remainder of this post will cover continuous deployment (referred to from this point as CD).
CD has two dimensions that determine its practicality. The first is related directly to the application. The second is related to the environment in which the processes are going to be implemented.
What I am about to tell you are “fightin’ words.” It is not (yet) widely accepted that CD is dependant on your application type and architecture. However, you will find that the CD pipelines that already exist share a lot of similarities in the nature of their application. And the companies that are opportunistic about CD but have not yet implemented it are running into a wall.
The aspects of application architecture that will prevent CD are:
Low transactions and low user base numbers are relative to your market and expectations from your users. It should be relatively clear to you whether you’ve satisfied these numbers or not. Beyond the attributes of your application, most organizations are attempting to implement CD in an existing delivery chain, which means there are existing processes and people to contend with. It’s possible to implement processes of CD without addressing the existing organization, but this usually leads to non-sustainable environments. Here are some key elements to consider:
One approach to responding to both of these challenges is choosing to emulate what the startups are able to do: build the application with the CD process from day one. Because most organizations already have existing applications, this is not possible. The best way to do this is to build a new version of the application in parallel, leveraging CD from the start. This will take time, but if your application was built with a services architecture, and a strong API layer for the backend, it should not be insurmountable.
Turning magic into reality is the real win. And many of the organizations who have successfully implemented CD have started with processes such as continuous integration first. They refined their approach, their tools, and their team structure in a way that gave them the confidence to move on to CD. They also focused on execution and sustainability, not just more releases direct to production.
Without jumping in on faith, the tool market will lead the way. And if your application lends itself to CD, and you are willing to do it right, you are ready for continuous deployment.
This blog was co-authored by myself and Simon Darken. Once a year, PagerDuty’s SREs get together for a three-day, in-person offsite. With the team spread...
A release is a set of customer visible and operational features that together provide a completely new or improved product capability. It’s something that’s meaningful...
600 Townsend St., #200
San Francisco, CA 94103
905 King Street West, Suite 600
Toronto, ON, M6K 3G9, Canada
1416 NW 46th St., St. 301
Seattle, WA 98107
5 Martin Place
1 Fore St,
London EC2Y 9DT
© 2009 - 2018