Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

1.9 KB
Raw Blame
# Build-only verification for the agent-orders image.
#
# cloudbuild.yaml (the real one) always ends in `gcloud run deploy`, and deploys
# are owner-gated, so there was no way to prove the image still builds without
# shipping it. This config runs the SAME Dockerfile against the SAME repo-root
# context and stops before push and deploy: nothing is tagged in Artifact
# Registry, nothing is deployed, no service changes.
#
# Building this image locally is not a substitute. The Dockerfile installs the
# full root workspace (3000+ packages) and compiles agent-payments-sdk, which
# needs more memory than a dev container typically has, and the local docker
# context is not filtered by .gcloudignore so it also walks a multi-GB dist/.
#
#   gcloud builds submit . \
#     --config workers/agent-orders/cloudbuild.verify.yaml \
#     --ignore-file workers/agent-orders/verify.gcloudignore \
#     --region us-central1 --project aerial-vehicle-466722-p5
#
# The --ignore-file narrows the upload to the paths this Dockerfile actually
# COPYs (~96 MB instead of the ~1.5 GB the repo-wide .gcloudignore allows, which
# re-includes dist/ and public/ for the three-ws-api image). Note that gitignore
# semantics cannot re-include a path whose parent directory is excluded, so that
# file re-includes /workers/ wholesale rather than /workers/agent-orders/.

# The project's default compute service account was deleted, so an unpinned
# submit fails with "Unknown service account".
serviceAccount: projects/aerial-vehicle-466722-p5/serviceAccounts/[email protected]

steps:
  - id: build
    name: gcr.io/cloud-builders/docker
    args:
      - build
      - --file
      - workers/agent-orders/Dockerfile
      - --tag
      - agent-orders:verify
      - .
    timeout: 1800s

options:
  machineType: E2_HIGHCPU_8
  logging: CLOUD_LOGGING_ONLY

timeout: 1900s