I have a very big production server in a VM with lots of web pages and SQL database code.
I want to set up VisualSVN so developers can work on the web and database code.
I have 2 options:
1) copy the production VM with all code, name this DEV-VM, and set up SVN on DEV VM
2) setup SVN on production VM so I don't have duplicate VMs that take up A LOT of space
Which option would you choose and why?
VirtualizationWindows Server 2012Microsoft SQL ServerJIRAProject Management
Last Comment
benc007
8/22/2022 - Mon
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Normally, we configure our VPN servers, as a standalone server, with plenty of internal disk space.
and then we create repositories for developers to check in and check out their code that they are developing.
benc007
ASKER
Andrew - Interesting!
Is your set up like this?
PROD server
DEV server <--- VPN <--- developer's local computer
Does each developer work locally on their own computers and then check in / out their code to a single DEV server where all of the code is? When the code is tested on DEV, then it's rolled out to PROD server?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
we actually have a few servers.... in our Development Team and Test Team
1. Production Server
2. Staging Server
3. Test and Dev Servers
All developers will submit code changes for revision purposes to SVN server, this allows them to checkout code to workstations, laptops from anywhere, make changes to code, and then submit those changes to SVN.
Code changes and tested on Test and Development Servers, when the change has been signed off and authorised, this also ties in with Service Desk requests for Incidents and Problems and also change control.
It then moves up to the Staging Server, where more testing is completed.... again signed off again before it's deployed to Production.
In this development framework, multiple revisions of code, can be in use at one time....e.g.
Production - Rev 1a
Staging - Rev 1b
Test and Dev - Rev 1c
RE: Developers have access to personal, shared and copies of production databases
Does this mean each developer has SQL database software installed on their machine eg. laptop or do you give them access to a VM with database software pre-installed and they code and work on the VM?
How do you track bugs and how do developers communicate in joint projects / code?
RE: Access is provided by using security based on AD Users and Groups granted on each Repo they connect to.
What access level do you give developers in AD for SVN?
and then we create repositories for developers to check in and check out their code that they are developing.