Earlier quoted context omitted.
except that - GitHub Action cache and build artifact handling is a complete shit show (slow upload, slow download and a lot of practical subtle annoyances, finished off with sub-par integration in existing build systems) - GitHub runners are comparatively small, so e.g. larger linker steps can already lead to pretty bad performance penalties and sure like I said, if you project is small it doesn't matter
I see the slow cache problem as universal. On a single-machine gitlab runner instance the upload to _local_ cache seems to take ages, double digit number of seconds for 100 MB archive.
The Pain That Is GitHub Actions
581–584 of 584 posts
Re: The Pain That Is GitHub Actions
#582We've all been there: $ git l * cbe9658 8 weeks ago rejschaap (HEAD -> add-ci-cd) Update deploy.yml * 0d78a6e 8 weeks ago rejschaap Update deploy.yml * e223056 8 weeks ago rejschaap Update deploy.yml * 8e1e5ea 8 weeks ago rejschaap Update deploy.yml * 459b8ea 8 weeks ago rejschaap Update deploy.yml * a104e80 8 weeks ago rejschaap Update deploy.yml * 0e11d40 8 weeks ago rejschaap Update deploy.yml * 727c1d3 8 weeks ag…
$ git l
* cbe9658 8 weeks ago rejschaap (HEAD -> add-ci-cd) Update deploy.yml
* 0d78a6e 8 weeks ago rejschaap Update deploy.yml
* e223056 8 weeks ago rejschaap Update deploy.yml
* 8e1e5ea 8 weeks ago rejschaap Update deploy.yml
* 459b8ea 8 weeks ago rejschaap Update deploy.yml
* a104e80 8 weeks ago rejschaap Update deploy.yml
* 0e11d40 8 weeks ago rejschaap Update deploy.yml
* 727c1d3 8 weeks ago rejschaap Create deploy.ymlRe: The Pain That Is GitHub Actions
#583Earlier quoted context omitted.
This is true because your CI steps will be running on a lower number of physical machines, ensuring higher cache hits?
Kind of - you can also pin runners.("This workflow runs on this runner always"). And caching just means not deleting the artifacts from the file system from the previous runs. Imagine building Android - even "cloning the sources" is 200GB of data transfer, build times are in hours. Not having to delete the previous sources and doing an incremental build saves a lot of everything.
tldr; "A cache is one or more files a job downloads and saves. Subsequent jobs that use the same cache don’t have to download the files again, so they execute more quickly."
It will probably still be slower than a dedicated runner, but possibly require less maintenance ("pet" runner vs "cattle" runner).
Re: The Pain That Is GitHub Actions
#584Earlier quoted context omitted.
It's doa, Sol.
Since you're using my first name in a weird and creepy way, I'll assume you're a hater. It's been so long since I've had one! Are you reactivating from the Docker days, or are you the first of a new cohort? That would be an exciting development, since getting haters is a leading sign of runaway success.