GitHub Actions CI/CD¶

This document describes the GitHub Actions workflows for the tradai-uv platform.

Overview¶

The platform supports dual CI/CD - both GitHub Actions and Bitbucket Pipelines run in parallel. This allows flexibility during migration and redundancy.

Workflows¶

1. CI (ci.yml)¶

Triggers: Push to main, tags v*, pull requests

Runs code quality checks on every change:

install → lint ─────────┐
        → typecheck ────┼→ (PR only) performance-test
        → test ─────────┤
        → security-scan─┘

2. Docker Build (docker-build.yml)¶

Triggers: Tags v*

Builds and pushes Docker images for all services to ECR:

Images are tagged with both the version (e.g., v1.2.3) and latest.

3. Publish Libraries (publish-libs.yml)¶

Triggers: Tags v*

Publishes the tradai-strategy library to AWS CodeArtifact for use by the strategies repository.

# The strategies repo consumes this via:
pip install tradai-strategy --index-url https://...codeartifact.../pypi/tradai/simple/

4. Deploy Lambdas (deploy-lambdas.yml)¶

Triggers: Tags v*, manual dispatch

Dynamically discovers and deploys all Lambda functions:

version ──→ build-wheel ──→ build-base ──→ discover ──→ build-lambdas ──→ update-functions
   │                            │              │              │
   │                            │              │              └─ Matrix: all lambdas
   │                            │              └─ Finds lambdas/*/Dockerfile
   │                            └─ Base image with tradai-common
   └─ Calculates version ONCE (prevents race condition)

Lambda Discovery: Automatically finds all directories in lambdas/ with a Dockerfile (excluding base/).

Manual Dispatch: Allows deploying to specific environments: - dev - Development - staging - Staging - prod - Production (default for tags)

5. Deploy Infrastructure (deploy-infra.yml)¶

Triggers: Manual dispatch only

Runs Pulumi infrastructure operations:

Usage: 1. Go to Actions → Deploy Infrastructure 2. Click "Run workflow" 3. Select stack and command 4. Review output before running up

Required Secrets¶

Configure these in GitHub Settings → Secrets → Actions:

Dual-Platform Setup¶

Git Remotes¶

# View remotes
git remote -v

# Expected output:
# origin    git@bitbucket.org:tradai/tradai-uv.git (fetch)
# origin    git@bitbucket.org:tradai/tradai-uv.git (push)
# origin    git@github.com:tradai-bot/tradai-uv.git (push)
# github    git@github.com:tradai-bot/tradai-uv.git (fetch)
# github    git@github.com:tradai-bot/tradai-uv.git (push)

Push to Both Platforms¶

# Single push goes to both (if configured with --add --push)
git push origin main

# Or push explicitly to each
git push origin main && git push github main

# Push tags
git push origin --tags && git push github --tags

Initial Setup¶

# Add GitHub remote
git remote add github git@github.com:tradai-bot/tradai-uv.git

# Configure origin to push to both
git remote set-url --add --push origin git@github.com:tradai-bot/tradai-uv.git
git remote set-url --add --push origin git@bitbucket.org:tradai/tradai-uv.git

# Initial push
git push github main --tags

Workflow Comparison¶

Troubleshooting¶

Cache Issues¶

# GitHub Actions uses UV cache at ~/.cache/uv
# If dependencies seem stale, the cache key includes uv.lock hash
# Changing uv.lock will automatically invalidate cache

Failed Lambda Discovery¶

# Check lambdas directory structure
ls -la lambdas/

# Each lambda needs:
# lambdas/<name>/Dockerfile
# lambdas/<name>/handler.py (or similar)

ECR Push Failures¶

1. Verify AWS credentials are configured
2. Check ECR repository exists: aws ecr describe-repositories
3. Ensure IAM permissions include ecr:GetAuthorizationToken, ecr:BatchCheckLayerAvailability, ecr:PutImage

Pulumi State Lock¶

# If Pulumi reports state lock:
pulumi cancel  # Cancel stuck operation
# Or manually unlock in S3

Adding New Services¶

1. Create service directory: services/<name>/
2. Add Dockerfile: services/<name>/Dockerfile
3. Update docker-build.yml matrix:

matrix:
  include:
    # ... existing services
    - service: new-service
      dockerfile: services/new-service/Dockerfile
      image_name: tradai-new-service

Adding New Lambdas¶

Lambdas are auto-discovered. Just create:

lambdas/
└── new-lambda/
    ├── Dockerfile
    └── handler.py

The next tag release will automatically build and deploy it.