configuration management Questions

We have a code review tool Atlassian Fisheye+Crucible already implemented, but we are using this with Perforce as our version control tool. Since Perforce has another code review tool "SWARM" we'd like to evaluate this tool. But need to know the benefits of using this tool over Crucible with fisheye.

SOme of the benefits I know is:

- efficient Pre-Commit code reviews
- No extra database to administrator
- Performance - Swarm executes transactions much faster than Crucible because Swarm is so tightly integrated with Perforce
- Ability to commit code from SWARm UI

I need to know from a core technical perspective if there is any other benefits.

I'm have promarily used Subversion in the past, and the structure we used was:

/branches    - Self evident name for branch management

   /int          - Integration branches

      /projectA_effort_q4_2014 - Integration branch for release on q4 of 2014

   /usr         - Individual engineers branches

      /fred    - Fred's set of branches

         /some_bug - Fred's branched from somewhere to fix some bug

      /sally    - Sally's set of branches

         /some_feature - Sally's branched from somewhere to add some feature

/tags          - Self evident name for tagging

   /projectA_v1.0 - Tag of projectA at version 1.0

/trunk         - Trunk for various projects

   /projectA  - ProjectA

   /projectB  - ProjectB

/vendor      - Repo path for storing pristine drops of 3rd party code used in various projects

   /acme     - Vendor name of a 3rd party source of code

      /superLib - Acme provides us the superLib

         /current - Latest drop of superLib

         /v1.0_drop - Tagged drop of superLib

         /v1.1_drop - Tagged drop of superLib


The machanics of this is to allow for segregated development with maximum traceablity. For example any propriatary changes specific to a project needed within superLib would happen within that project, and only the pristine changes from the vendor would be within the /vendor area, then merged into the project to minimise merge errors.  Users brnach off the integration branches to their own staging areas in usr to integrate new functionality of fix issues and merge them back into the integration branches once proven.  The CM, PM, EM, and PVM would be responcible for merging the integration branch to the trunk project and tagging the trunk project versions.


Our current system is TFS based, and is really porrly managed - it was a historical conversion from ClearCase to TFS and there is no clear deliniation as described above.  In fact, it's more like a shot gun of tags and branches, without a really good organzation of where the root of changes should reside, and there's multiple code forks even though 90% of the code is shared.
I was looking to see if it makes sence to refactor the release structure into something like the above, but I'm not sure if it makes sense for TFS and the documentation I can find on TFS doesn't really describe best practices or typical work flows, and the rest of the users here are actually more familier with ClearCase as TFS was a corporate edict of standardization that was pushed onto them.
If you are familier with a better flow or best practice for TFS, please share as our current structure is unmaintainable and unscallable for validation and test purposes.

Thanks much,


A new project we got will force us to add a few more testers for the duration of the project (estimated around 8 months). We will probably outsource this extra testing alongside us. My question really has to do with any advice or tool anyone of you uses or knows of that will be a smart way to manage this effort?

I mean models or domain specific languages to represent complex scm process (version control, identification, build management etc.). Maybe exist some approach allows to represent bridge from abstract process to choise of real tools and implementation.

For exapmle, in software development MDA approach exist, where are 3 kinds of models with different level of abstraction. Are some analogs exists for software configuration management?

How have others solved the resourcing justification for Build / Release engineers? Based on number of supported developers? number of tools? number of deployments? are there base line ratios or other industry standards based on specific products or supported platforms?

I have no clue on bitbucket but read it supports Git. Trying to understand how do we choose which VCS should a company use if code is not public & team size is 100+developers.

Bitbucket or Git on linux based system?Dont wish to explore the paid version to start with.

Any thoughts please share.


after upgrading one database from synergy 6.5 to 7.1 checking on the MDL_INFO file for the recent upgraded datbases i.e "x" and another one with version 7.1 i.e "y" I found a differance which is "IBM Rational Synergy Fix Pack" found only on Y file database and not found on X databases (which is reacnetly upgraded)

is there any clarification for this please




By Param M - June 29, 20144 Answers


I am working an project to migrate from SVN to Clearcase UCM. Kindly guide me if any one have step by step process to move with or without revision files from SVN to Clearcase UCM.


Thanks in advance.

I am trying to connect to dimensions via Desktop client and am getting the error as "failed to connect to the dimensions server" .

The same error comes when connecting via dmcli as well.

the oracle is running while we check the server.
can you help us to resolve this.

By LaShawn Dorsey - June 11, 20141 Answer

Should the FCA be started after system testing or user acceptance testing?  Currently on my project, I start the FCA after system testing and begin the PCA after user acceptance testing.


CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.