Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B buck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • buck
  • Issues
  • #2405
Closed
Open
Issue created Feb 26, 2020 by Administrator@rootContributor

buck shared cache capabilities

Created by: AlexDreyfuss

hi,

I have been trying to configure buck to use a shared cache on the network. when on both machines i put my project on /home/local/bucktest/application it works great. when i change the dir to the project to lets say /home/local/bucktest1/application the access to the cache fails. probably because the rule key hash changes.

Is there a a way that buck includes only relative paths into the hash computation? It would be too hard to force developers to use buck on preset dirs and paths?

Assignee
Assign to
Time tracking