VCS plugin with CVS - workflow

[jcm]

Hi all. I'm using the VCS plugin with Jalindi igloo and CVS. It works well for us, but I'm having a hard time integrating it with our current workflow.

We use two database instances:dev and prod. We currently do all of our development in dev, and then move the code to the prod database. We occasionally refresh the dev db by using rman's duplicate database.

I'm thinking the right way to do this is to use a cvs branch for the dev db, and then merge it back into prod, but I'm not sure how to get the VCS plugin to do this correctly. Is anyone doing anything similar? Any suggestions would be appreciated.

 

[Brian Baker]

With our team's process, we label both the application source code and the database source code with each new build. Then, when I want to update our production environment, I use our source control tool (VSS) to extract the scripts for all the code that has changed since whatever build is currently in production and then manually apply those to the production database.

I find that much easier than trying to setup different source branches to represent the different environments.