CVS Teamsite integration

Hi

Can anyone please share their thoughts on integrating CVS(for code management) with teamsite(for content management).

Are there any resources already which gives more information on CVS and teamsite integration.

Thanks
Teamsite Guy

Find more posts tagged with

Comments

Adam Stoller

There's nothing out of the box in terms of this integration - and a lot depends on *how* you want to integrate the two systems.

Do you want to pull from CVS into TeamSite?
Do you want to push from TeamSite into CVS?
Are you trying to do both and keep them synchronized?
Are you trying to convert from CVS to TeamSite and are trying to preserve historical information?
etc.

On the general side - basically it's a matter of using CLT's both from CVS and TeamSite to coordinate the transactions. From TeamSite you can use either Custom Menu Items or Workflow (or a combination of the two)

--fish
(Interwoven Senior Technical Consultant)

teamsite_guy

Thanks fish.

Basically we have teamsite for all content, Microsoft VSS for code and Opendeploy for deploying. Till now all binaries/jar files were being loaded into teamsite.

Now we are getting CVS and ANT for source code and build. And we are looking to integrate CVS into the system,so that CVS replaces VSS.

I think you asked me the right questions.

We would probably want to "pull from CVS into Teamsite", the reason being the deployments can done using OpenDeploy. Am I correct?

Can you please tell me what is the best way to do this "pulling". Should every event in CVS be mapped to a corresponding event in Teamsite. Is it good to have every user in CVS have a corresponding workarea in Teamsite? How can the synchronization be maintained between CVS user's checkout area and his "Teamsite Workarea".

I appreciate your suggestions.

Thanks
Teamsite Guy

Adam Stoller

The specifics of how you use (or intend to use) CVS will determine the specifics of the implementation - but some things I would suggest are:
(a) always label the files you want to pull from CVS so that they can be easily extracted via CVS CLTs
(b) create a custom menu item that prompts for (among possible other things) the label, and probably the repository path.

As you figure out the command line calls to retrieve the files you want to retrieve, build up the CGI script for the custom menu item (or workflow cgitask)

It will take a bit of trial-and-error to get it right, so be prepared to "design" the solution first before trying to "implement" it.

--fish
(Interwoven Senior Technical Consultant)

tvaughan

I'm faced with the possibility of something like this coming up, and I'm leaning towards doing some semi-fancy deployments with DNR scripts.

Basically, I'd like to keep source code off the IW server and on some dedicated development server where those donkeys can go an compile their test jars all they want. I'll periodically give them a dump of recent content so that they can see if their code is working with the look & feel.

When they tell me that they're ready for a release to a QA server, I can do a reverse deployment so that the IW server grabs the jars off the dev server, brings them in to a dedicated branch for their source code, then deploys both the jar(s) and content to the QA server, whereupon I do a DNR script to bounce the app and web servers out on that box.

I'm anxious to keep developers off the TS box because my whole company's content will be controlled off TS and I don't want to slow the box down by letting every Tom, **** and Harry developer have space on that machine. Hence, the complicated **** deployment process described above.

Tom

teamsite_guy

Thanks fish and Tom.

Instead of pulling the files from CVS to Teamsite, we are thinking in lines of mapping the the CVS user's drive onto his workarea in Teamsite. So, that when a CVS user gives a specific type of build using ANT, the compiled jar and/or class files fall in his corresponding Workarea in Teamsite.

Is there any inefficiency in this method, that you can think of. We are planning on doing this mapping only for some CVS users.

Thanks
Teamsite Guy.

XPATH.zip

tvaughan

Sounds pretty smart.

I like that you're limiting (via ant) the users allowed to run builds that end up dumping code in TeamSite.

Mapping the drive is also nice, because it means no clock cycles end up being burnt on your TS server due to javac calls.

Nice setup.

Tom

teamsite_guy

Thanks Tom.

Thanks
Teamsite Guy