Skip to main content

Config

Prerequisites: Permissions​

User must have Privileged Role Administrator for setup.

Cloud Connection​

Create Connection

Creating a cloud connection sets up a consent for Warpbuild CI Enterprise application with the permissions required by WarpBuild to manage runners. Provide the tenant ID and subscription ID to verify the connection after the consent and permission configuration (arm deployment) is complete

Stack​

Create Stack

Creating a stack creates the infra configuration provided and uses the storage account and container for cache and telemetry.

Create Stack

The stack name, storage account and container, and region cannot be changed after creation.

Custom Runners​

Custom Runners

  1. Spot instances are useful for short jobs that can be interrupted and can lead to significant (~70%) cost savings.
  2. One or more instance types in priority order can be chosen. The Github workflow uses a single runner label but picks the instance type based on availability.
  3. The minimum disk configurations are:
    • Size: 256GB

Best practices:​

  1. Choose a minimum disk configuration of:
    • Size: P20

Throughput and IOPS automatically managed by Azure. Refer: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd-size

Limitations​

  1. BYOC Azure does not support import flow for stack creation.
  2. Snapshot-based runners are not available for BYOC Azure.
  3. BYOC Azure currently only enabled for East US. For adding more regions, please reach out to [email protected].

Coming Soon​

  • Resource tagging