This message was deleted.
# performance
s
This message was deleted.
a
Normally CI have push + pull enabled (more controlled environment) and local users have just pull
a
Yes but we are a team of 20 devs we run CI(PRs) concurrently. When building my PR does that invalidate the cached modules for master or another PR?
a
No, it doesn't invalidate them. Imagine build cache just as a hash map: MapTask inputs, Task output. So that map can contain cached entries for different branches/PR/etc. Build cache itself is not aware of what branch your build is from, or how one task is related to another. And invalidation happens only if you delete entries in a map: aka you clear build cache.
1
a
Thanks so much for clearifying this
🙌 1
i
Personally I have: • developers only pull from cache • CI in PRs only pulls • CI in
main
or tags pulls and pushes
a
@Ivan CLOVIS Canet I can confirm that enabling push on CI also speeds on CI for my use case for where I have the following: 1. Compile and build cache 2. Run unit tests which also the compile code, but since we have now enabled push on the compile job so the unit tests dont have to re-build