We switched to fetching and hard resetting for efficiency, but this is
sensitive to work on the HPC that changes the state of the git environment.
E.g., at some point the git remote was set to ssh instead of https,
which caused the build not to be able to pull the most recent state of the
repo, which resulted in a period where we were overwriting the last weeks
predictions instead of appending new ones.
Delete and recloning using https is a more robust approach because it avoids
any state influencing the behavior of the pipeline.
We switched to fetching and hard resetting for efficiency, but this is sensitive to work on the HPC that changes the state of the git environment. E.g., at some point the git remote was set to ssh instead of https, which caused the build not to be able to pull the most recent state of the repo, which resulted in a period where we were overwriting the last weeks predictions instead of appending new ones.
Delete and recloning using https is a more robust approach because it avoids any state influencing the behavior of the pipeline.
Closes #394.
Co-authored-by: Henry Senyondo henrykironde@gmail.com