See related documentation:

    Token 

    1. Visit CircleCI home
    2. Choose the relevant organization
    3. Click Runners
    4. Click Create resource class (keep track of the namespace and label)
    5. Utilize the token value below.

    Configuration 

    [[circleci.tier4.runner]]
# A resource class token.
token = ""

# --------------------------------------------------------------------
# Optional: defaults inlined.

# Limit the number of cores consumed concurrently by all jobs.
# For cost buckets see https://doc.cedarci.com/financial/pricing/ and
# https://doc.cedarci.com/feature/tier/ for the tier4 cost adjustment.
# The default will adjust to contract/custom limit.
concurrent_core = 30

# The number of CPU cores or partial cores, ranging between 0.25 and 16.
# Values may also be given in milicpu (ex. 1500m = 1.5).
# The CPU to Gigabytes of memory will be maintained at a 1:2 ratio.
cpu = "2"

# The URL of the CircleCI server for use by runner.
runner_api = "https://runner.circleci.com"

    Workflow 

    Update desired workflow jobs to run on cedarci using the $namespace/$label chosen.

     jobs:
   build:
+    resource_class: cedarci/fast
     docker:
       - image: alpine
     steps:
       - checkout
       - run: echo "speedy"

    Capability 

    The runner does not current support setup_remote_docker option on jobs. Let us know if that is important to you via our contact e-mail.