| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Broker code in CVS |
« View previous topic :: View next topic » |
| Author |
Message
|
| messg_wb |
 Posted: Wed Sep 15, 2010 12:59 pm Post subject: Broker code in CVS |
 |
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
Hi - I am trying to implement CVS in our environment for broker code and am coming across a road block, Hope you guys can help me
I defined multiple environments (IT / QA / Prod) in CVS, I am able to sync my local project with IT and am able to deploy to IT broker by extracting from code from corresponding environment in CVS, In the next step, while deploying to QA, I would like to extract code from IT-CVS and update QA-CVS and deploy from QA, How do I update the code in QA (with the one in IT), I tried cvs import/update/export, nothing seems to be working, Can somebody suggest me fix for this issue
Thanks |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Sep 15, 2010 1:14 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
which CVS you are using?
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| messg_wb |
| Posted: Thu Sep 16, 2010 6:44 am Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
Gayathri,
Here is the version:
Concurrent Versions System (CVS) 1.11.17 (client/server)
Copyright (c) 1989-2004 Brian Berliner, david d `zoo' zuhn,
Jeff Polk, and other authors
CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Sep 16, 2010 6:57 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
1. Get your QA-CVS working directory ready.
2. Copy the files from the working directory IT-CVS to the new working directory QA-CVS (do not copy the contents of the `CVS' directories, of course).
3. Working in the new working directory QA-CVS , use commands such as cvs update and cvs diff to figure out what has changed, and then when you are ready, commit the changes into the repository.
go through backing up a repository section
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| messg_wb |
| Posted: Thu Sep 16, 2010 10:47 am Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
Thanks Gayathri, I am doing the same but there is one big drawback with this procedure, everytime I deploy something in QA, I copy the files from IT to QA so I am loosing the history of the QA (To be more clear, on day 1, I deploy to QA so i copy the contents of IT to QA, and then I do multiple deployments to IT, assume 3 versions, on day 5, I deploy to QA so again I copy the contents of IT to QA so instead of seeing only 2 versions in QA history, I see more versions)
Is there workaround for above prolem ? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 16, 2010 10:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
CVS itself at this point is an old technology. There are newer version control tools that are just as free but more powerful and more modern - such as SVN or git or even Jazz.
What you are doing is a fairly atypical setup. Most source control strategies have a single repository, and then releases into QA and PROD are tagged or otherwise identified within that. |
|
| 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
|
|
|
|
