The only thing I can think of is we have 3 build agents and commonly we're doing custom builds for a past revision.
Here's a case I just tried:
- Latest cs is 23277 and Agent 1 is currently building it
- Agent 2 last built 23275
- I Run Customized with 23275 as the revision
- Agent 2 starts the build and updates to 23277, even listing 23277 as the custom revision like in my previous post.
Tried it on another plan:
- Latest cs is 23277
- Agent 3 last build 23276
- Run Customized with 23275 as the revision
- Agent 3 picks it up and updates to 23277 instead
Nothing else of much interest. Single stage and job in bamboo. First task is checkout repo. Repo using main branch, no other branches active. Repo is linked across all build plans. Seems to happen on all build agents and plans.