Cloud build failing to pull from github after changing history.

Build & Deployment Build Automation
1

After I made some history-changing modifications to my repo to move all my large files to Github LFS, Cloud build is failing to pull due to not being able to compare changes with a commit that no longer exists.

The exact error is as follows:

31: GIT: Get current revision
32: GIT: Current revision is 6d02ef55cc9f32453c3c27bf17897141e26d8e6d
33: GIT: Get changeset between 3fa0788acb314837aa7c8e3d03a850ba19d75737 and 6d02ef55cc9f32453c3c27bf17897141e26d8e6d (max 15)
34: Error getting changeset! git '--git-dir=/BUILD_PATH/japa.armok-vision.armok-vision-windows/.git' '--work-tree=/BUILD_PATH/japa.armok-vision.armok-vision-windows' log '-15' '--no-color' '3fa0788acb314837aa7c8e3d03a850ba19d75737..6d02ef55cc9f32453c3c27bf17897141e26d8e6d' '--pretty=raw'  2>&1:fatal: Invalid revision range 3fa0788acb314837aa7c8e3d03a850ba19d75737..6d02ef55cc9f32453c3c27bf17897141e26d8e6d

Is there any way to fix this without deleting and re-making the cloud build project?

2

Looks like there is a problem dealing with that case. Will get that fixed.

In the meantime, I’ve manually fixed up some data that should allow you to continue building again. I’ve started a build for you to confirm.

3

Thanks, the build pulled better this time, but still failed to pull anything from Git LFS, causing a build failure.

4

Ok, one more try. Looks like your project was on our old checkout method that didn’t support LFS properly (I’m assuming someone in support moved it over for you previously). I’ve updated it to the correct checkout method and kicked off another build.

5

Built successfully, thanks!