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
  • #9135

Closed
Open
Created Apr 14, 2015 by Administrator@rootOwner

Gitlab packages not cached locally by composer?

Created by: huglester

Hello,

I am not sure, how to describe the problem. But for example, we are using composer to download packages from github/gitlab.

And packages (tags) from github, are cached by composer:

  - Installing symfony/process (v2.5.11)
    Loading from cache

it is loading from cache, if it was at least once downloaded in the past.

But for example, for our gitlab packages, we always get this:

  - Installing pyro-modules/forms (v1.1.1)
    Cloning 72fc88a91e21a7f10275d0fa06b62bcb9a17a380

no matter how many times it is downloaded. It is always cloning from gitlab, but not picked up from local cache?

So now the question is, the problem is in gitlab, or maybe in my composer/satis setup?

Thank you

Assignee
Assign to
Time tracking