People throw the terms “availability” and “uptime” around a lot, but depending on what you’re monitoring, the definition of these terms may change. In this article we use the narrow definition, accessible, to explore the various options Uptrends has for checking availability on websites, APIs, and servers.

If you’ve been following along, the last two articles explained the CI/CD (Continuous Integration/Continuous Delivery) processes. In this article, we look at how Uptrends fits into those processes. Uptrends can fit into your CI/CD process in several different ways. For example, you may want to use Uptrends for the testing and monitoring portions, include your monitor updates as part of your automation processes, or both.

In the first article, we talked about CI or Continuous Integration. This post looks at the second half of the CI/CD acronym, Continuous Delivery. Continuous delivery takes the build originating in the CI process and puts it into an acceptance environment for further evaluation before promoting the code to production (the released version). To back up a moment, CI is the planning, coding, testing, and building of software in a rapidly repeating process.

Continuous integration is the first half of the acronym CI/CD, with Continuous Delivery completing the second half. In this three-part article, we look at the two halves of CI/CD to define and understand them, and then, in part three, we talk about how Uptrends fits into your CI/CD processes. Let’s get started at the beginning with continuous integration.