|
|
To speed up builds Gitlab uses a cache where it will store the dependencies that it wants to maintain between different stages and jobs. The location of this cache and the method for maintaining it can be configured through the `gitlab-ci.yml` file in the repo. More information about Gitlab caches can be found at [https://docs.gitlab.com/ee/ci/caching/](https://docs.gitlab.com/ee/ci/caching/).
|
|
|
|
|
|
Sometimes the cache will need to be manually cleared. This will sometimes happen when the local cache gets out of sync with the actual repository. In such instances, Gitlab will fail to run a job because it thinks that the resource in its local cache is unchanged. One way this manifests itself is when the build script claims that a branch hasn't changed but in reality, the branch ***has*** changed or doesn't even exist in the current repo.
|
|
|
|
|
|
To fix this issue the cache must be cleared. One way to do this is to click the `Clear Runner Caches` on the `CI/CD -> Pipelines` page. If this doesn't resolve the issue, the cache can also be manually cleared.
|
|
|
|
|
|
First make sure you know how to [use sudo on Summit-QA](using-sudo-on-summit-qa).
|
|
|
|
|
|
1. Login to summit@summit-qa.research.vt.edu
|
|
|
2. `sudo su rm -r /home/gitlab-runner/cache/*` |
|
|
\ No newline at end of file |