Skip to content

Allow choosing cache compression algorithm explicitly #389

Closed

Description

@Vampire

Copy of actions/toolkit#544 for using this possibility here in case it got added to actions/toolkit first :-)

Currently the compression algorithm for caches is chosen implicitly according to what tools and versions are available on an environment.
It would be nice if it were possible to instead manually select the compression algorithm, including choosing no compression algortithm.

The use-case is, that I build something on one environment and want to test it on multiple others.
I don't want to use artifacts for that, as that is not really their intention imho and you also cannot delete the artifacts.
Imho the cache with the workflow run id as cache key should be better suited for inter-job file sharing.
But you currently have the problem, that if you for example build on a gzip environment like windows-latest and then try to restore on a zstd environment like windows-2016, you get a cache miss.

actions/toolkit#543 would improve on that example, but as soon as you swap it around and build on windows-2016, wanting to test on windows-latest, actions/toolkit#543 would not help.
So it would be nice if you could manually select the compression algorithm in the cache-action (and therefore having it possible here first), to be able to choose the lowest common denominator (including no compression) that can be understood on all part-taking environments.

Activity

  1. github-actions commented on Dec 23, 2021

    @github-actions

    This issue is stale because it has been open for 365 days with no activity. Leave a comment to avoid closing this issue in 5 days.

  2. Vampire commented on Dec 23, 2021

    @Vampire
    Author

    .

  3. pratikbin commented on Jan 20, 2022

    @pratikbin

    +1

  4. self-assigned this
    on May 11, 2022
  5. added and removed
    area:granular-controlIssues related to granular control in saving or restoring cache
    on Oct 19, 2022
  6. lvpx commented on Nov 16, 2022

    @lvpx
    Contributor

    Hi @Vampire @pratikbin the idea of choosing own compression algorithm is not planned to be worked on in the near future. Please visit #984 and provide feedback on the current proposed changes to tar compression. Closing as wontfix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions