Academy / Sync App Flow & Deployment / SyncApp Deployment — Branch Deploys and Dev Environment (Part 2)

SyncApp Deployment — Branch Deploys and Dev Environment (Part 2)

Lesson 5.6 ⏱ ~7 min

💡 Why This Matters

Branch deploys are how you test your changes on a real SyncApp before merging. This is the final gate between your code and production — getting this workflow right means fewer bugs make it to the weekly release.

🎯 What You'll Learn

  • How to deploy a specific feature branch build to a specific source ID for testing
  • How to verify the deployed version is running by checking the version number in WAM after an Update
  • The development workflow: write code → deploy branch → test → raise PR → merge → deploy main
  • How to use the Dev Deploy UI (separate URL for dev environment)
  • How credential caching issues can cause login errors when switching between prod and dev deploy UIs

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

The Branch tab in the Deploy UI shows builds from all in-progress feature branches. Select your branch's latest build, choose Linux/AMD64, enter your test office's source ID, and deploy. Click Update to trigger an immediate restart. Check WAM to confirm the version number has changed. This is the standard pre-PR testing workflow. For the dev Deploy UI, use the dev-specific URL — logging out and back in resolves credential caching issues that arise when switching between prod and dev environments.

🏷 Key Concepts

Branch Deploy Pre-PR Testing Workflow Version Verification in WAM Dev Deploy UI Credential Caching Issue Deploy Workflow: Branch → Test → PR → Main → Release

Key Takeaways

01Always deploy your branch to a test office before raising a PR — this is the team's expected practice
02Confirm the version number in WAM after clicking Update — if unchanged, the update may not have taken effect
03The dev and prod Deploy UIs are separate URLs — use dev for development testing, prod only for actual releases
04Credential caching issues between prod/dev UIs are resolved by logging out and logging back in
05The full cycle: code change → branch deploy → test → confirm in WAM → raise PR → merge → prod deploy