I'm looking for a good way to migrate changed code from development to test to production servers, for a group of less than a dozen developers. Right now, we use TOAD with team coding. The problem is that sometimes a developer will lock the package, make some changes, move it to development or test, then it gets stuck. If I need to alter the package, I have no choice but to wait for it to complete testing, be rolled out to production, then the team coding lock released. Do you have any suggestions on how multiple people can concurrently work on packages? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Code Migration
- Thread starter jaxtell
- Start date
SantaMufasa
Technical User
Jaxtell,
I have been very impressed with TortoiseSVN Subversion for software version management. Click the link, above, for a full description and let us know your reactions.
![[santa]](/data/assets/smilies/santa.gif "[santa] [santa]")
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
I have been very impressed with TortoiseSVN Subversion for software version management. Click the link, above, for a full description and let us know your reactions.
Mufasa(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
- Thread starter
- #3
Dave,
I am familiar with subversion (I'm am supposed to upgrade our java apps to use that instead of CVS). But unless there is a plugin or something I missed, its basically an entirely manual process. Like, I'd have to check out the file, make sure it matches production(as well as test and development servers), do my changes, compile on development server and make sure to check in my changes at the same time. But it still means I need to check that I'm not overwriting someone else's changes every time I compile, right? I won't know there is a conflict until I go to check it in. I'm not sure what SVN provides that team coding (microsoft source safe) does not.
I am familiar with subversion (I'm am supposed to upgrade our java apps to use that instead of CVS). But unless there is a plugin or something I missed, its basically an entirely manual process. Like, I'd have to check out the file, make sure it matches production(as well as test and development servers), do my changes, compile on development server and make sure to check in my changes at the same time. But it still means I need to check that I'm not overwriting someone else's changes every time I compile, right? I won't know there is a conflict until I go to check it in. I'm not sure what SVN provides that team coding (microsoft source safe) does not.
- Status
Similar threads