Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Persistent cache/ in successive CI builds?

See original GitHub issue

I have noticed that in every CI build, for example this, there are a lot of:

[x] GET: https://X.Y/Z
[x] 200 OK

calls which probably take up the majority of the build time. Is it not possible to persist the cache/ directory across successive CI builds (so redundant GET calls are avoided)?

Issue Analytics

State:
Created 4 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

2reactions

kmykcommented, Mar 18, 2020

One of the advantages of online-judge-verify-helper is the “bundle” feature. We would like to write our libraries with multiple files, but most judge services require single .cpp files to submit. The “bundle” feature solves this problem. It converts .cpp files and #include-ed many .hpp files into the single .cpp file.

0reactions

GaurangTandoncommented, Mar 18, 2020

Hi, thanks for your helpful responses! I will look into the other repo you linked to. Does it have any other significant advantage over oj-tool apart from generating awesome documentation like this one?

Top Results From Across the Web

Caching in GitLab CI/CD

A cache is one or more files a job downloads and saves. Subsequent jobs that use the same cache don't have to download...

Persisting Data Overview

Caching persists data between the same job in different builds, allowing you to reuse the data from expensive fetch operations from previous jobs....

Webpack 5 persistent cache is not usable in CI environments

In CI, a common paradigm is to store cachable data between runs to cut down on execution time. The webpack 5 persistent cache...

Caching Dependencies and Directories - Travis CI

Caches lets Travis CI store directories between builds, which is useful for storing dependencies that take longer to compile or download. Note that...

Persistent cache - Dagger Documentation

However, sometimes you can't keep a persistent Buildkit daemon along your CI/CD. For instance, if you use a GitHub Actions runner, your daemon...