Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9933

Closed
Open
Created Dec 29, 2015 by Administrator@rootOwner

How does GitLab CI caching work?

Created by: kahwee

I'm a little confused how cache works and am not able to take advantage of it well. Can you see if I did anything wrong?

I previously cache (with untracked set to true) two directories at global level -- node_modules/ and dist/

Subsequently, I decided that cache dist/ is a bad idea and removed it.

Now, when I push an update and a rebuild occurs, I noticed dist/ is always in the cache together with node_modules no matter what.

Is there any way I can get rid of dist/ being cached?

Thanks.

Assignee
Assign to
Time tracking