All use cases
QA & test engineers
Reproduce the bug on the exact build the customer has
Deployment history tells you which commit is live where, so you test the right thing.
Before Fenwave2 hours waiting
“Cannot reproduce. Which version is actually on prod right now — the tag or the hotfix branch?”
What the wait costs
Two hours testing a build the customer never had, and a bug report closed as "cannot reproduce" that reopens next week.
"Cannot reproduce" is very often "reproduced against the wrong build". The deployment history records which commit went to which environment, when, and by whom — so the first step of triage becomes a lookup. Once you know the commit, a branch environment gives you that exact build to test against.
How it works
- 01Open the service in Deployments and read the history for that environment.
- 02Identify the commit that was live when the customer hit the issue.
- 03Reproduce against a branch environment built from that commit.
- 04Attach the environment URL and the commit to the defect.