Rely.io
  • 📌What is Rely.io?
  • 💡How Rely.io works
  • 📑Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • 📚Guides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • 🖥️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • 🥇Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚡Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • 🤖Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • 🔌Plugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • ⚙️Invite Users
  • 🛡️Security & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • 🏥Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page
  • Overview
  • Installation Guide
  • Required permissions
  • Steps to Integrate Bitbucket with Rely.io

Was this helpful?

  1. Plugins & Automation
  2. Plugin Installation Guides

Bitbucket

PreviousAWSNextFlux

Last updated 7 months ago

Was this helpful?

Overview

Bitbucket is a platform for hosting and versioning code, facilitating collaboration among developers. Leverage the power of Bitbucket's vast repository data within Rely.io for a comprehensive view of your software lifecycle.

Installation Guide

Required permissions

During the configuration process, you'll be asked to authorize the App to have specific permissions in your account for the plugin to function properly: Read

✅ Account

✅ Issues

✅ Build Pipelines

✅ Project

✅ Repositories

✅ Pull Requests

✅ Team Membership

The necessary permission scopes will be automatically filled in for you so you don't have to worry about that.

Steps to Integrate Bitbucket with Rely.io

  1. Open the Rely.io platform and start by navigating to the Plugins page in the Portal Builder.

  2. Click the Add Data Source button and select Bitbucket.

  3. You'll be redirected to Bitbucket's app integration form, login to your account.

  4. Submit the form by providing the necessary permissions

  5. You'll be redirected back to Rely.io

  6. Provide an expressive name to this integration that allows you to easily identify the source

  7. Click Submit to finalize the integration.

To prevent pulling outdated or stale data from your tools and flooding your catalog with unactionable entities, our plugins are set by default with policies to reduce noise.

For instance in the case of Git providers:

  • Repositories with no activity over the last 3 months are ignored

  • Repositories that have been archived are also ignored

  • All entities related to ignored repositories (Pull Requests, Issues, Deployments, etc.) are consequently ignored

After you add the Bitbucket plugin, an entity discovery run will be triggered. The initial discovery run can take up to a few minutes. By the end of this discovery run:

  • New blueprints will be added to your data model

The plugin periodically updates all retrieved entities to ensure they stay in sync with their external counterparts.

Once the initial discovery run completes successfully you should see your GitLab plugin under the Active section of the data sources page.

Entities retrieved from the data source will be added to the page for you to either approve or reject them

↗️
🔌
Rely.io
Discovery