| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Version / Change Control PVCS Best Practices |
« View previous topic :: View next topic » |
| Author |
Message
|
| spfdgio |
 Posted: Mon Sep 20, 2004 7:01 am Post subject: Version / Change Control PVCS Best Practices |
 |
|
Apprentice
Joined: 09 Oct 2002
Posts: 36
|
Hello! Our shop is in the process of upgrading from WMQI v2.1 to WBIMB v5.0 fp4. My 4 WMQI developers are used to the checkin and checkout functions being done in the Control Center, and now with WBIMB these functions are externalized via an eclipse plugin to an external product (such as CVS, PVCS). Our shop standard is to use PVCS, so I installed and successfully activated the plugin to PVCS. I showed them how to put WBIMB projects under PVCS control, how to technically interface with PVCS, but then realized that I was not giving them strategic information needed to design and implement real version and change control. For example, the developers were used to doing checkin and checkout of msgflows and msgsets and doing their own deploys into production because there was no way to integrate with PVCS. Now we are integrated and we are discussing that the developers should be working with our PVCS production control group to move WBIMB objects from acceptance into production prior to a production deployment of new code. What I do not have is a set of 'best practices' for what should be under PVCS and what / how to best implement change control specifically with WBIMB.
Let me be clear about my intention - it is not to 'lock down' anything to upset our developers, but instead to understand how other WMQI/WBIMB systems administrators have dealt with this issue and what (if any) experiences and challenges were faced and overcome. Do I advocate for a policy with only the .bar files being moved by our change control group or also msgsets and msgflows? Do I advocate for all source files being included with the .bar files to ensure we know what is being deployed? Would there turn-up any reasons for the WBIMB administrator (me) to override checkin status? How about subflows...or .esql files....how have others handled these new files in version/ change control? Any help is appreciated.......Thanks very much
Dan in Harrisburg, PA |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Sep 20, 2004 7:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your developers should keep flows and sets under version control, for change management and source history reasons.
You may or may not want to put bar files under version control. Generally, when working with version control systems, one does not version control the results of a build (binaries or jar files or whatever), with the assumption that one can rebuild from any release at any point.
Whether or not your developers do their own build and deploys is a separate question. They should certainly be doing this in the development environment. The build process for version five, if I've been following the various attempts so far, is not completely fully automatable yet. You still need to actually open the tooling. Therefore, I'd recommend that production builds be done from sources taken out of PVCS. This will ensure that the developers have actually put the right code and etc into PVCS and that you CAN rebuild from any release at any point.
I would treat WBIMB as just another development environment, and use the same PVCS procedures that you use for every other development environment - in terms of how and what are kept in version control, who does builds for what environment, etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Empeterson |
| Posted: Wed Sep 22, 2004 12:00 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
Where did you get the plug in from? I went to eclipse.org and to merant's site and cant seem to find it. Thank you.
_________________
IBM Certified Specialist: MQSeries
IBM Certified Specalist: Websphere MQ Integrator |
|
| Back to top |
|
|
| spfdgio |
| Posted: Thu Sep 23, 2004 11:14 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2002
Posts: 36
|
The plugin at eclipse.org is not current (v7.5?) and wont work with the WBIMB Toolkit since the Toolkit is based on WSAD v5 and Eclipse 2 code. We went to v8.0.0.8. When you install the PVCS client code for v8.0 (since Merant went to Serena from my knowledge, it is now called Serena Professional Version Manager) on Windows, select 'custom' and you can check the box for 'Merant Plugin for Eclipse'. The next screen will ask you for the path to Eclipse which you can add something like C:\Program Files\IBM\WebSphere Business Integration Message Brokers\Eclipse. The install will complete. When you bring up the WBIMB Toolkit, it will recognise that the plugin was moved in as a pending configuration change and ask you to process the changes for 'Merant Team Plugin 2.0.9'. Select the boxes for this and click finish - it will install and close/reopen the toolkit to a welcome screen to help you setup. You will want to read the 'Merant Version Manager IDE Client Implementation Guide' chapter 18 'WSAD v5 - Eclipse 2' for details on function. I did ask Serena support to post the PVCS v8 plugin on the eclipse.org website, but apparently it is still not there? Hope this helps.....Dan  |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Wed Oct 06, 2004 8:42 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
|
| 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
|
|
|
|
