Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #5036 move to gitolite3
Actions
Summary
site admin
move to gitolite3
I don't have to wait for 10mn that my permission modifications are serialized on FS
- Create 1'000 repo in g2 (acknowledge that's GIT_REPO_UPDATE is slow)
- Move to g3 (http://gitolite.com/gitolite/g2migr-example.html + package: http://fr2.rpmfind.net/linux/epel/6/x86_64/repoview/gitolite3.html)
- Verify that speed of GIT_REPO_UPDATE is better
- Test with 10'000 repo
- Verify that there is no functionnal regression (all git admin operations, including gerrit migration an replication, permissions, email, HTTPs, ...)

https://groups.google.com/d/topic/gitlabhq/g5_AXKbPEe8/discussion
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [x] Is it exploratory?
Empty
Details
#5036
Manuel Vacelet (vaceletm)
2013-10-14 18:13
2013-09-20 10:31
3135

References
Artifact links
Referencing story #5036

Artifact Tracker v5

epic #5035 Gitolite performance
rel #4931 6.6
Referenced by story #5036

Artifact

art #5335
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2013-09-27 17:46
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes