As an Atlassian Solution Partner and World Class Software Development Finalist, 2024-2025, Atlas Bench is proud to help teams streamline their DevOps workflows with Compass, Atlassian’s developer experience platform. In this blog, we’ll walk you through how to connect Compass to the key tools in your DevOps pipeline, enabling your team to reduce friction, boost visibility, and move faster.
Whether you're managing a few microservices or hundreds, integrating Compass into your workflow helps your team stay in flow and focused. Below, we’ll cover integration with source control, CI/CD, incident management, and observability, and share best practices along the way.
Watch a quick video overview where we walk through this blog in under 4 minutes:
Start by syncing your repositories with Compass to automatically import and catalog your components.
How to do it:
Navigate to the Components tab in Compass. Choose “Add component from repository.” Authenticate with GitHub or Bitbucket using an OAuth or token-based connection. Select the repositories you want Compass to monitor. Compass will automatically extract component metadata, ownership, and key details.
Best Practice:
Standardize naming conventions across repositories to ensure clean mapping and better discoverability in your catalog.
Get real-time deployment status updates in Compass and connect each component with its delivery flow.
How to do it:
Use webhooks or Compass API integrations to connect your pipeline tool. When a pipeline completes a deployment (success or failure), push metadata to Compass. Link each CI/CD job to the relevant component in Compass.
Example:
A Jenkins job can post deployment outcomes via a REST API call directly to the Compass component page, showing when and how often deployments occur.
Best Practice:
Include deployment status in scorecards to track system health and reduce mean time to resolution (MTTR).
Make incidents visible directly in Compass and tie them to affected components.
How to do it:
Enable Compass integrations with Jira Service Management or set up Compass Operations. Configure Compass to track incidents by component ownership and labels. View active and historical incidents directly on component dashboards.
Best Practice:
Align Jira Service Management projects and Compass components using shared tags or naming conventions to improve traceability.
Surface health metrics and alerts within Compass so developers don’t have to context-switch.
How to do it:
Use Compass APIs or out-of-the-box integrations with Datadog and New Relic. Push telemetry data like latency, error rates, and uptime to each component. Display live health metrics on Compass dashboards.
Example:
If a latency spike is detected in New Relic, it appears in the Compass activity feed and triggers a notification via Jira or Slack.
Best Practice:
Define clear thresholds for alerting and ensure monitoring spans all critical dependencies.
Integrating Compass into your DevOps pipeline isn’t just about connecting tools; it’s about creating a unified, developer-friendly experience. Atlas Bench helps teams set up Compass correctly from day one: mapping components, defining scorecards, aligning toolchains, and creating golden paths to production.
We make sure every integration is secure, scalable, and tailored to your workflow, so your developers spend less time on configuration and more time building.