Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 164
    • Issues 164
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Merge requests
  • !319

Closed
Created Dec 21, 2021 by Georges Racinet@gracinet🦑Owner
  • Report abuse
Report abuse

Draft: new caching system in CI

  • Overview 1
  • Commits 12
  • Pipelines 2
  • Changes 3

Instead of the gitlab-prebuilds tarball, this is closer to upstream pipelines: a first job provides the dependencies either as artifacts or by updating a big cache.

The main advantage is that we had no reliable way to update the tarball only when needed (changes: is an approximation that's actually wrong in many important cases).

Thanks to this, we should not need to worry about changing cache keys, or updating the tarball separately any more. The price to pay is some more latency (most of which is actually time to first clone, which is another kind of issue anyway).

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: topic/heptapod/ci-multi-caches-final