Managing 150+ Git and SVN repositories in one self-hosted platform
NDA-protected web development customer uses RhodeCode to centrally manage Git and SVN repositories in one self-hosted platform, keeping source code under its own control while simplifying repository, user, and permission management.
- Repositories
- 150+
- Users
- 50+
- Version control systems
- 2
- SCM platform
- 1 self-hosted
Managing Git and SVN across modern and legacy projects
Development environment included both Git and SVN repositories, reflecting the different ages and technical requirements of the projects being maintained.
Running separate management systems for each version control system would have increased administrative overhead and made it harder to manage repositories, users, permissions, and version history consistently.
Team needed a reliable way to centralize source code management without forcing legacy SVN projects to migrate simply to standardize tooling.
One management layer for Git and SVN
RhodeCode provided a single platform for managing both Git and SVN repositories while allowing developers to continue using the version control tools they already knew.
Modern web development projects could remain on Git, while existing and legacy applications could continue using SVN.
Repository access, users, permissions, change tracking, and version history could all be managed centrally instead of through separate administration workflows.
Self-hosted source code management under full control
- 00150+ Git and SVN repositories managed centrally
- 0150+ users supported
- 02One self-hosted SCM platform
RhodeCode was deployed as a self-hosted source code management platform within the customer's own infrastructure.
This allowed the team to keep proprietary source code under its own control while providing one central location for more than 150 Git and SVN repositories used by approximately 50 users.
The self-hosted model also gave the team control over where source code was stored and how repository access and permissions were managed.
Simpler repository management without forcing migration
- 002 VCS technologies managed in one platform
- 01Reduced administrative complexity
- 02No forced migration of legacy SVN projects
RhodeCode became the central source code management layer for Git and SVN repositories across projects with different technical histories.
Developers could continue working with familiar Git and SVN workflows, while repository management, users, and permissions were handled consistently through one platform.
Team avoided the need to maintain separate SCM management platforms for Git and SVN and retained full control over its source code infrastructure.
"RhodeCode has effectively become our central source-code management platform, giving us the flexibility of multiple VCS technologies with the convenience of managing them through a single self-hosted system."
- Automotive · 2,400 engineers Four years, no frozen release Read →
- Digital identity & security · Global Thales: Managing 11,893 repositories across global teams Read →
- Financial services · Frankfurt An audit finding closed with a screenshot Read →
- Defence · air-gapped Installed on a network with no route out Read →
- Research computing Search that kept working as the repository count grew Read →
- Medical devices Evidence a notified body accepted Read →
Would this approach fit your organisation?
Bring your repository count, your VCS mix and your compliance constraints. We will tell you honestly whether a staged migration is the right answer for you — sometimes it is not.
- Bring
- repository count, VCS mix, seat count
- Constraints
- regulator, classification, contract
- We answer
- within 24 hours, by an engineer
- Contact
- sales@rhodecode.com