Description of the issue
When a pull request is changed on GitHub (by a new commit, for example), Bitrise fails to fetch the latest commit, being stuck in an old build. Forcing the developer to use the “rebuild” button.
Basically, if a new commit B is added to the PR on top of A, the virtual machine still downloads, and tries to build A.
Examples:
Initial PR build:
Git Checkout Configs:
- Commit: d7163b4882a38e7377c3f4cac875d97661221c3d
- Tag:
- Branch: feature/logout
- CloneDepth:
=> GIT_CLONE_COMMIT_HASH
value: d02155c8169f592956c9de664e75ace01f0c7179
=> GIT_CLONE_COMMIT_MESSAGE_SUBJECT
value: Merge d7163b4882a38e7377c3f4cac875d97661221c3d into 024b2d3468334d9535859d130f92e55631057f9f
Follow build with problems on cache:
Git Checkout Configs:
- Commit: 13734af5794ea9115165efc4fb22e34dba91ffc4
- Tag:
- Branch: feature/logout
- CloneDepth:
=> GIT_CLONE_COMMIT_HASH
value: d02155c8169f592956c9de664e75ace01f0c7179
=> GIT_CLONE_COMMIT_MESSAGE_SUBJECT
value: Merge d7163b4882a38e7377c3f4cac875d97661221c3d into 024b2d3468334d9535859d130f92e55631057f9f
Environment:
Where did the issue happen?
Bitrise.io: Android & Docker, on Ubuntu 18.04
Which build Step causes the issue and which version of the step?
Git Clone Repository, 4.0.11
Reproducibility
-
_Does a “Rebuild” help?
SOMETIMES. It is needed some “rebuild” actions to the build to work -
_Does a rebuild without caches help?
NO -
_Does the issue happen sporadically, or every time?
EVERY TIME -
_Does upgrading the build Step to the latest version help?
NO -
_When did the issue start?
May 17th