Today we are thrilled to announce the general availability of Delta Cloud and Team Syncing! While Delta Local mode is great for solo projects, scaling intelligent test selection across development teams requires syncing. Delta Cloud coordinates your mappings automatically so teams and CI/CD pipelines run in sync without duplicate mapping builds.

Why Cloud Sync Matters

In a standard local setup, your test mapping database is restricted to your machine. If a teammate adds a test, deletes a line of code, or updates a file, you won't have that coverage record until you run the entire test suite locally again to update the SQLite file. Delta Cloud eliminates this by serving as a single source of truth for test mappings.

Delta Cloud Sync Workflow
1. Local Dev Changes Code Developer creates a branch and edits source code files.
2. Fetch Mappings from Cloud Delta CLI queries the remote database for code-to-test mappings.
3. Run Affected Tests Instantly Only the precise affected test subset runs locally.

How to Configure Cloud Mode

Switching your repository to Delta Cloud takes less than a minute. Run the login and tracking commands in your project's terminal:

bash 
$ delta login
# Enter your credentials...
   Authentication successful. API key saved.

$ delta track --name my-application-repo
   Repository tracked successfully!
Repo ID: aa251edf-8d2b-4e1b-9fca-72bf7e8ea7bc

CI/CD Pipeline Integration

To keep the cloud database updated automatically, configure your CI/CD workflow to rebuild and push mappings on merges to your primary branch:

yaml 
- name: Update Delta Mappings
  run: |
    delta build-mapping
    delta push
  env:
    DELTA_API_KEY: ${{ secrets.DELTA_API_KEY }}

Once active, any developer pull or local run will automatically query the latest coverage mapping pushed from the pipeline, reducing testing latency for everyone on the team.