You can clone with
HTTPS or Subversion.
If branch being updated in Git isn't the deploy branch, invalid deployment card appears and then closes.
If it is the branch being deployed then, commit id/author data if available needs to be populated right away before the payload is transferred.
similar to issue #251
The view we're seeing here is a default view just to tell the user that something is happening.
This occurs for example when we start getting a change pushed from the user, at first we don't have any information on it but when it takes a long time we still want to show the user that we are doing something, this is why there is no commit id or author data.
The scenario with the update not in the deploy branch is when we get the change so we show that we're doing something (InProgress) but then we didn't deploy due to the fact the deploy branch didn't change so the deployment simply disappears.
I will close this one. This will be addressed the same way as #253 (pranav is cleaning this up).