From the course: Advanced GitHub Actions

Unlock the full course today

Join today to access over 24,200 courses taught by industry experts.

Caching between workflow runs

Caching between workflow runs - GitHub Tutorial

From the course: Advanced GitHub Actions

Caching between workflow runs

- [Instructor] When we integrate code, we often use tools like Yarn, Maven and PIP to identify and download dependencies. On our local systems, these tools can create a copy of the dependencies so we don't have to keep downloading the same files over and over again. This is known as dependency caching. In GitHub Actions, most workflows start with a new virtual environment. So out of the box, we lose the benefit of being able to cache dependencies. If we're not smart about it, we might experience long build times that use up our precious build minutes or slows down developer velocity. However, there are two approaches for caching that we can use to speed things up. If you're using JavaScript, Python, Java or Ruby, the setup actions for these languages allow cashing to be configured easily. Each action has a parameter that enables caching. Most of them take an input named cache with a name of the dependency…

Contents