Docker layer caching based on current branch




our workflow includes spinning the primary container in the remote docker environment and, within that one, building our NodeJS app image, including the npm dependencies. This works fine and docker layer caching is used (which is a great time saver). If the package.json or shrinkwrap change, it will trigger a rebuild (my dependency chain has changed, I need to update it).

However, if this happens on a developer branch, it might affect the rest of the branches, given the builds land on the same host, is that correct?

If so, could you advise on how we could prevent this, e.g. is there a way to scope the docker layer caching mechanism to the current branch, as it was with CircleCI 1.0 caching?


closed #2

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.