We can have a problem when

1. Agent 1 takes Build A-1 from Plan A
2. Agent 1 loses network connectivity to the server
3. Agent 1 is marked as "going down" and goes off-line since the server could not receive the heartbeat. Lock on Plan A is released
4. Build A-2 is triggered. Starts building on Local Agent
5. Agent 1 comes back online, still with Build A-1.

At this point, things go wrong. Logs gets streamed in a funny way (since we assume that only one build is ever building), Build A-2 is saved with Build A-1. JIRAns have an example of this.

We should make sure if an agent has been marked as going offline, it is never allowed of come back (maybe check startup timestamp) when an Agent comes back online.

Needs further investigation and if the problem is too large to safely fix on branch, then we can defer it to fixing on trunk.