| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CVS usage |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqwbiwf |
 Posted: Wed Jan 27, 2010 11:59 am Post subject: CVS usage |
 |
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
Hi,
We are planning to setup a new CVS server for our developers to store the WBI flows/sets and bar files. Currently, we are having issues with keeping up with the code changes in stage, pre-prod and prod environments, and hard to track back to the exact prod version even with the usage of all tags while building a bar file!
With this new CVS server in place, from a best practices perspective, would it make sense to have multiple respository paths (one for stage, one for pre-prod) and have multiple workspace paths for the developers? So that we can completely isolate Stage and Pre-prod environments? And one "Admin repository" created with just the admins able to access the flows/sets that are deployed to Production?
Ofcourse, one other concern is not to end up creating too many repositories but still be able to manage the code without creating a lot of confusion between stage, pre-prod and prod code.
Thanks! |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jan 27, 2010 2:29 pm Post subject: Re: CVS usage |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqwbiwf wrote: |
Hi,
We are planning to setup a new CVS server for our developers to store the WBI flows/sets and bar files. Currently, we are having issues with keeping up with the code changes in stage, pre-prod and prod environments, and hard to track back to the exact prod version even with the usage of all tags while building a bar file!
With this new CVS server in place, from a best practices perspective, would it make sense to have multiple respository paths (one for stage, one for pre-prod) and have multiple workspace paths for the developers? So that we can completely isolate Stage and Pre-prod environments? And one "Admin repository" created with just the admins able to access the flows/sets that are deployed to Production?
Ofcourse, one other concern is not to end up creating too many repositories but still be able to manage the code without creating a lot of confusion between stage, pre-prod and prod code.
Thanks! |
Once it has left development and until it has reached production your CODE should NOT undergo ANY change.
The only things to change across the environments should be the configurable properties of the bar files.
What you might want to set up is a trunk and branches. You will need to be able to merge the branches to the trunk at some time... or just let a branch die...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 28, 2010 5:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You should probably use SVN instead of CVS. It's just as free, just as user friendly, but more capable and reliable. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
