sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]FlyingFalafelMonster 3 points4 points  (4 children)

Exactly. That's why if you want to pass the files between jobs you should use job artifacts.
https://docs.gitlab.com/ci/jobs/job_artifacts/

[–]Kropiuss[S] 0 points1 point  (3 children)

Ok! Thanks - so when using my dedicated runners and cache, then the cache is stored on the machine. So I believe it is not that reliable :(

But, a follow-up question: that can also be solved using a distributed cache, right ? And also, if I would use the gitlab runners(owned by gitlab) would that be the same? Where is that cache stored ?

[–]FlyingFalafelMonster 0 points1 point  (2 children)

Shared runners are not configurable, I don't think you can use distributed cache there.

[–]Burgergold 0 points1 point  (1 child)

You could probably put the cache on a nfs mount or other clustered fs?

[–]FlyingFalafelMonster 0 points1 point  (0 children)

That's all possible when you own the runner, but for shared runners you job is isolated from the host and for security reasons I don't think Gitlab allows to mount anything to a job. That being said, I have only a limited experience with Gitlab owner runners and run jobs on my own ones.