Integrate your CI/CD Pipelines with OpsLevel

Embracing a microservice architecture typically also means deploying much more frequently, which can seem scary. But favoring many incremental deploys is actually a sound risk mitigation strategy since changes tend to be smaller and more isolated.

However these patterns mean you have a lot more deploy events to keep track of–and sift through when something does go wrong. So OpsLevel is making this process simpler with out-of-the-box integrations for Jenkins, Octopus, and GitHub Actions.

The last two weeks of deploy events for a service
Review and access all a service's deploy events from the operations tab in OpsLevel

With these integrations (and our generic deploys endpoint) all your crucial deploy events can be tracked, searched, and accessed from OpsLevel, alongside the other valuable service metadata that provides complete context for all your services.


If you’re using Jenkins, OpsLevel’s Jenkins plugin makes sending us your deploy events easy and highly customizable:

  • Send OpsLevel notifications for all builds, or use build configurations to include or exclude particular builds or pipelines from sending notifications
  • Override any of the default notification parameters by inserting a Jenkins pipeline step, or use a freestyle project post-build action

Learn more about the integration in our Jenkins docs.


If you’re using Octopus, OpsLevel’s Octopus Community Step is for you. Our integration is based on our OpsLevel CLI and has community step versions for both Windows/Powershell and Linux/Bash .

One you’ve installed the CLI and the correct community step, you can then add the OpsLevel notification step to any of your Octopus projects. Any of the default values in the OpsLevel step can be overridden as needed.

Learn more about the integration in our Octopus docs.

Github Actions

If you’re using GitHub Actions, OpsLevel’s integration is for you. Like Octopus, this integration uses OpsLevel’s CLI. Once the integration is installed and configured, the OpsLevel action can be used with any event trigger. Triggering on a push to the main branch will be the most common workflow.

Learn more about the integration in our GitHub Actions docs.


If you’re using a different CI/CD tool, you can still send your deploy events to OpsLevel via our generic deploys integration. In fact, you can also send us other relevant configuration events like infrastructure or feature flag changes, as seen in the screenshot above.

Centralizing all this activity in a single pane of glass makes it easier for anyone in your engineering organization to understand and troubleshoot services they may not be experts in.

If you’re ready to start tracking your deploys (and other configuration changes) in your service catalog, request your OpsLevel demo today.

Previous Post: Create a Culture of Continuous Improvement with Personalized Service Maturity Notifications
Next Post: How Paul Osman thinks about long-term strategies, open telemetry, and the value of boring systems

Learn how to grow your microservice architecture without the chaos.

Not ready for a demo? Stay in the loop with our newsletter.