We should implement some kind of ring buffer of build caches on the build runners. If the runner has a cache, it uses it; if not, oh well.
This is going to be a great feature. I am currently building a Go project and my dependencies get downloaded for each task. Temporarily there could be some sort of
before_taskskey in the manifest, that is run at the same level as the distro package installation. I could then run
go geton all my dependencies. Thoughts?
What advantage would that provide over just running
go getin a normal task?
Referring to this build: https://builds.sr.ht/~tristan957/job/11249.
My dependencies are fetched once per task. Am I doing something wrong?
That entire page represents ajoband each log represents ataskin that job. So far as I can tell the only time your (go) dependencies are fetched is in the build task, right?
I'll pull a different build. One sec. That on efailed due to docker for some reason
Ah, docker hangs on builds.sr.ht for unknown reasons, I'm afraid.
I don't really know what to do about this.
Yeah that is interesting to say the least. And I thought Docker within Docker was funky. I'll follow the issue for fun though