Fixes: expected docker context is increased due to WF merge#1893
Conversation
lognaturel
left a comment
There was a problem hiding this comment.
Approving to fix CI in the short term and because I agree we should review tagging and version generation as part of what @alxndrsn and @garethbowen are working on to pre-build images.
An alternate small fix would be to set the fetch depth to something like 50 instead of 0 (unlimited). That should pull the tagged commits we need without increasing the download size so much.
|
We've talked about this plenty but it's another example of how our installs are not exactly reproducible. CC @yanokwa |
|
Seems like the new file count window is very big. |
|
Talked with @alxndrsn on Slack, and he is suggesting that we increase the min-size value as well so that expected size window is not too large. I'll create a new PR to do that. |
Size of git db (objects) has increase quite a bit after merging web-forms code into central-frontend, therefore increasing expected file size of docker context.
I am wondering if there is a way not to include git objects in the docker context but we rely on them to generate version.txt. Maybe once we start publishing built images we can get rid of them.
PS: Found this issue while working on a separate issue. To understand the root cause I rerun GH Actions on
nextandmasterbranches even those were failing with everything (OS, runner, git version, docker version) being same e.g. https://github.com/getodk/central/actions/runs/25595119221/job/76010520926. Only difference I could see wasgit/objects/pack/pack*.Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)