Skip to content

CircleCI: seperate caches based on core modules measurements #769

@tlaurion

Description

@tlaurion

The idea here (to replicate on #768 GitlabCI):

  • Have ./crossgcc unique compiler cache based on modules/compiler file being measured
  • Have ./build/* unique build cache based on modules/* files being measured

That way:

  • bash scripts modification won't require to rebuild any module
  • When modules/* change, only the build cache will be remade and made unique
  • When ./crossgcc requires to be remade, crossgcc unique cache will be remade and unique

As of right now, the cache is made a single time and never remade, based on:

- save_cache:
          key: heads-{{ .Environment.CIRCLE_USERNAME }}-{{ .Environment.CACHE_VERSION }}

and

 - restore_cache:
          key: heads-{{ .Environment.CIRCLE_USERNAME }}-{{ .Environment.CACHE_VERSION }}

Failed attempts to specialize CircleCI caches happened here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions