Ilya,

On 5/15/21 5:30 PM, Илья Шипицин wrote:
I've found that we do not cache "download-cache" and "opt" folders,
thus we build BoringSSL on every build (no cache).

I tried to enable cache

https://github.com/chipitsine/haproxy/blob/master/.github/workflows/vtest.yml#L46-L53

github does not like such caching keys:

Error: Key Validation Error: Linux-Ubuntu, gcc, no features cannot contain
commas.


Tim, do you have an idea how to fix this ?


I suggest the following:

- Cache based off the matrix.ssl value, because that determines what type of SSL lib we download and build. - If we want to cache something else in the future, then we use a separate cache head for that specifically. - And then use `steps.XXX.outputs.cache-hit != 'true'` to check whether you need to build anything or not.

See also: https://github.com/actions/cache#example-workflow

Best regards
Tim Düsterhus

Reply via email to