Request for Dedicated (Non-Shared) Hardware Option for Atlassian-Managed Runners in Bitbucket Pipelines

XMLWordPrintable

    • 1

      Description:
      We are currently using the Bitbucket Premium plan and leveraging Atlassian-managed runners for our CI/CD workflows. While Atlassian-managed runners provide a convenient and fully managed build environment, we have a requirement for dedicated (non-shared) hardware resources for our pipelines.

      Feature Request:
      Please provide an option for Atlassian-managed runners to run on dedicated hardware, where compute resources (CPU, memory, etc.) are exclusively allocated to our organization’s pipelines and not shared with other Bitbucket Cloud customers.

      Business Justification:

      • Enhanced security and compliance for sensitive builds.
      • Predictable and consistent build performance.
      • Meets requirements for organizations with strict data isolation or regulatory needs.
      • Reduces the risk of noisy neighbor issues on shared infrastructure.

      Current Limitation:
      At present, Atlassian-managed runners operate on shared infrastructure, and exclusive hardware allocation is only possible via self-hosted runners, which increases operational overhead.

      Request:
      Introduce a premium or add-on option for Bitbucket Pipelines that allows customers to provision dedicated, Atlassian-managed runner hardware for their exclusive use.

            Assignee:
            Unassigned
            Reporter:
            Karthick S
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: