Onboard Bitbucket to DevOps Change Velocity — Workspace

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 3 minutes to read

    • Connect to your Bitbucket instance using the DevOps Change Workspace playbook to discover repositories.

    Before you begin

    Complete the tasks specified in the Getting started with DevOps Change Velocity topic.

    Role required: sn_devops.admin or sn_devops.tool_owner

    Procedure

    1. Navigate to Workspaces > DevOps Change Workspace and use one of the following options to open the Playbook to onboard Bitbucket.
      OptionSteps
      Homepage
      1. Select Connect a tool.
      2. On the  Connect to a tool  modal, select Bitbucket from the Code category.
      Applications module
      1. Select Applications (Applications icon.) from the primary navigation.
      2. Select an existing application, or create one. To create an application, see Create an application - Workspace.
      3. From the  Recommended actions  pane, select the  Connect a tool  card.
      4. On the  Connect to a tool  modal, select Bitbucket from the Code category.
      Tools module
      1. Select Tools (Tools icon.) from the primary navigation.
      2. From the Capability list, select Coding.
      3. Select Connect a tool.
      4. On the  Connect to a tool  modal, select Bitbucket.
      Important:
      If you want to discover and track tool objects like repositories while connecting to the tool, you must connect your tool from the Application module.
    2. Specify a name for the tool in the Tool name field, and select Next.

      Connect to the Bitbucket tool screen

    3. On the Bitbucket instance details playbook activity:
      1. Enter the URL of your Bitbucket instance.
      2. Enter the login credentials of the global admin for the Bitbucket instance.
      3. If your Bitbucket instance is attached to a MID Server, select the MID Server option and enter its details. A MID server is required if your tool instance is hosted on-prem. For more information about MID server, see MID Server selection.
    4. Select Connect.

      Connect to the Bitbucket tool - Enter instance details screen

    5. Permission checks are run on the credentials that you entered.

      Permissions required and permissions that are available are displayed. If you want to enter credentials with better permissions, select Re-enter credentials. For detailed information on all the required permissions, see Bitbucket permissions in Permissions required for DevOps tools.

      You can choose to continue with the tool connection even if you don't have all the required permissions.

      Connect to Bitbucket tool - Permission checks screen

    6. Select Next.
    7. Specify the access for the tool.
      1. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.
        The tasks these users in the groups can perform depends on the role assigned to them.
        • DevOps Tool Owner role: Can view and edit the tool.
        • DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
        • DevOps Administrator role: Can edit all tools.
        • Other DevOps roles: Can view the tool.
        Note:
        If you don't select a group and skip this step, all users with the DevOps Tool Owner role will be able to edit the tool.
      2. If you choose to control access to the tool, the All App Owners can view and associate tool objects to applications option becomes available for selection.

        This option enables all users having the DevOps App Owner role to access the tool. If selected, they’ll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.

      3. Select Assign.

      Specify tool access.

    8. Select the repositories for which you want to configure webhooks automatically.

      Real-time notifications are ideal to maintain the most up-to-date information particularly for automating change requests.

      You can also set up webhook by configuring it manually. Alternatively, you can choose to enable nightly polling to fetch data system for any tracked repositories by setting the Enable Polling property to Yes.

    9. Select Configure.
      Connect to the Bitbucket tool - select items to configure screen

      To configure manually, select Configure manually. See Configure webhooks in Bitbucket manually for more information.

      Important:
      • If you're connecting from the Home page or Tools module, the connection is complete and you're taken to the Summary page.
      • If you're connecting from the Applications module, then repositories available in your instance are discovered. You can track and import historical data from them.
    10. Select the repositories that you want to track and associate to the application from the Select repositories to track playbook activity.

      Connect to the Bitbucket tool - select repositories to track screen

    11. Select Next.
    12. From the Summary page, review the details of the successfully connected Bitbucket tool.

      Select View tool record to review the details of the connected instance and the repositories discovered from it.

      Connection summary

    Result

    You’ve successfully onboarded your Bitbucket tool to DevOps Change Velocity.
    Note:
    If your tool credential changes, you must also update the credentials in DevOps Change. For more information, see Update third-party tool credentials in DevOps Change Velocity.