Home/ Questions/Q 7493873
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T17:13:09+00:00

Currently all my team members connect to a CENTRAL SVN server and they commit

  • 0

Currently all my team members connect to a “CENTRAL SVN server” and they commit their code.
The SVN Server is being used by many other teams.
As such, if one of my team member makes a mistake, it impacts other guys creating a hue and cry 🙁 …. 🙂

What I want to do is to create an “INTERMEDIATE SVN Server” to which all developers will connect to. They commit their code to “INTERMEDIATE SVN Server” and then build/integration testing is done at this “INTERMEDIATE Server”. If all tests are OK, then code is further committed from INTERMEDIATE Server to the “CENTRAL SVN Server” thus giving cleaner code to a greater audience.

I know this is basic stuff, but can someone help me realize this by linking me to some documentation/scripts, around this topic. Thanks in anticipation.

I use Tortoise as SVN client.

Regards,
Amol

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You are over thinking this – you don’t need an additional SVN to perform code review before committing to trunk. You would simply create a daily branch (or tag) then merge after review. This is the default way to handle this…

    See this link for general help: http://svnbook.red-bean.com/en/1.7/index.html

    Branching and Merging: http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html

    • 0