Why our SVN cannot have 2+ users modifying a code simultaneously
We have SVN installed in our server and are using it everyday, but only 1 user per code.
Prior installing and starting to use some time back, we think we tested if 2+ users can share and make changes to the same code; seems to work.
Now we are in the desperate need to have 3 programmers modify a specific code so we can finish the task in an appropriate time. Unfortunately, we can't work it together.
Is this the way SVN works? Or do we have a procedure or a configuration problem?
Prior installing and starting to use some time back, we think we tested if 2+ users can share and make changes to the same code; seems to work.
Now we are in the desperate need to have 3 programmers modify a specific code so we can finish the task in an appropriate time. Unfortunately, we can't work it together.
Is this the way SVN works? Or do we have a procedure or a configuration problem?
Do you get any error?
ASKER
Don't think so, but will check when get to a PC...
ASKER
While we are getting to the PC (we're in another are), we need to know:
Does SVN, our running version VisualSVN 2.5.5, has that capability of permitting 2
or more programmers modify the same code simultaneously ?
Please answer this to have this clear at our end.
Thank you.
Does SVN, our running version VisualSVN 2.5.5, has that capability of permitting 2
or more programmers modify the same code simultaneously ?
Please answer this to have this clear at our end.
Thank you.
ASKER
There is no errors displayed.
The problem is occurs when the programmers are updating the same code that they are working with. For example:
The problem that occurs is that the when Programmer 2 "commit", it deletes the work of programmer 1 by replacing the code with just his changes. All work of Programmer 1 is lost and replaced.
The problem is occurs when the programmers are updating the same code that they are working with. For example:
Programmer 1 and 2 open a copy of the code in the morning
Programmer 1 finishes making 10 changes at 11am and click commit to save his changes.
Then programmer 2, changes one button in the code and makes a commit at 430pm
The problem that occurs is that the when Programmer 2 "commit", it deletes the work of programmer 1 by replacing the code with just his changes. All work of Programmer 1 is lost and replaced.
I guess you have a process issue first. Programmer 2 should get a latest to merge his changes before checking in.
ASKER
How do we go around this?
The programmer are not in the same room so they can't say to each other "I'll update first". This has become frustrating and the programmer are asking to purchase a more expensive solution to centralize coding.
When we decided on SVN it was with EE help and all have been working excellently. Now that this problem happens the programmer are saying it never worked.
Before deciding on throwing away SVN we would greatly appreciate EE feedback on this.
The programmer are not in the same room so they can't say to each other "I'll update first". This has become frustrating and the programmer are asking to purchase a more expensive solution to centralize coding.
When we decided on SVN it was with EE help and all have been working excellently. Now that this problem happens the programmer are saying it never worked.
Before deciding on throwing away SVN we would greatly appreciate EE feedback on this.
the svn server should solve all the issues you have.
from your description i assume you have installed two servers which are sharing the same storage (?). actually, for svn you may have only one server. then all participants are "clients" for example tortoise svn clients which connect to the same one server. if it is made that way any check-in would be managed by the server and you will see those changes by looking into the log. if a second developer would check-in the same sources, the server would do a merge, either automatically if there are no conflicts or manually, by leading the second developer into a merge dialog.
Sara
from your description i assume you have installed two servers which are sharing the same storage (?). actually, for svn you may have only one server. then all participants are "clients" for example tortoise svn clients which connect to the same one server. if it is made that way any check-in would be managed by the server and you will see those changes by looking into the log. if a second developer would check-in the same sources, the server would do a merge, either automatically if there are no conflicts or manually, by leading the second developer into a merge dialog.
Sara
ASKER
We have SVN installed in one server, Windows server. The clients computer we use vb2022 sync to the server. Hope his info help you help us.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry about that, mistype: we meant vb2012.
We are working just as you say: when we open a solution, a copy is exported to our PC.
Please advice.
We are working just as you say: when we open a solution, a copy is exported to our PC.
Please advice.
ASKER
As curios as it seems the problem was partial data being download. Made sure that the data is downloaded completely locally and it worked.
ASKER
- we have on the server installed: VisualSVN 2.5.5 and tortiosSVN 1.7.
- we used to have VB2005 and configured to access SVN (but never seems to work
when trying 2 or more programmers modify a code)
- now we have recently upgraded to VB2012 and also using our current SVN.
Please advice based on this information what can we do to have 3 programmer work on the same source code and consideration shold we follow.
Like alwasy, thank you all EE very much!