configuration management

Articles

Testing Release Management in the Cloud

For many organizations, cloud computing has transitioned from a hyped buzzword into a reality in regards to their business operations. Many more enterprises are realizing the benefits of remote hosting IT services rather than local IT management, especially as managing and operating IT networks and services is not getting any easier.

Dan Joe Barry
Aspects of Release Management

The lack of proper planning can doom any project, or team. By involving every stakeholder, release management is made easier by helping to ensure customer satisfaction. Deadlines are able to be met, and with the exact product your customer had in mind.

Iniyan Charles's picture Iniyan Charles
Release Management and Deployment Essentials

Business requirements often dictate how changes in release management are addressed. But by following some essential practices and core beliefs, database deployment does not have to result in the headaches once caused.

Uri  Margalit's picture Uri Margalit
Need help with ClearCase performance on VMware client machine

We are using VMWARE client machines to run builds. On the VM clients all clearcase activities take more time compared to a standalone system. I want to know if there are any basic parameters on VM and ClearCase that can be fine tuned for better overall performance.

We are aware that clearcase on VM is slower when compared to standalone system. We are looking to better the ClearCase VM performance which is at 500% when compared to stand alone system performance.

A labelling activity takes 7 mins on standalone system which on VM machine takes 46 mins.

Your experience wrt to ClearCase on VM would be very helpful.

CM_CD
In Subversion, is there a way we can avoid the .mak file being commited to the repo though its modified in the developer workspace?

In SVN , a user is forced to "Checkout" the entire directory containing a source file even though he wants to modify only one file.

Assume a VB project containing .frm, .bas and .frx & .mak files. When user checks out the entire project and makes changes to just .bas file , and uses the VB project properties to configure the build, the .mak file invariably gets updated and becomes a checked out item. When user tries to commit his changes..both *.bas & .mak files get commited to the repository.

Suggestions..anyone ???

vijayboomi
How do I block checkout when the file is checked out in ClearCase

I am trying to create a project which has many document files (excel, xml). They are difficult to merge, and I am trying to find a way to block check out when the files are checked out already by another user.

I considered using single development stream, but it still allows multiple users to check out files at the same time.

I would appreciate if you can share the tips.

bluemoon
What is the appropriate branch-merge strategy for an audited company?

First of all, I'm brand new here. Secondly, I searched the forum for an answer to my question but failed to locate one. Apologies if this has been answered elsewhere, please let me know if so. Thirdly, my long & complicated question. (Sorry! CM is hard:)

At my company we are revisiting our branch/merge policy due to some production mishaps. I suspect we may be doing things sub-optimally, but would like your input.

Branch policy in a nutshell: branch from Trunk, using the newest code. I.e., start your project with the latest and greatest (untested code.)

Merge policy in a nutshell:

philbryant
In ClearCase, is there any way to write config spec rules to point prior version to LATEST with out using LABELS.

If i have 5 versions, config spec should point me to 4th version.

it should happen to all files, so i cannot use LABEL.

Thanks in advance.

Thanks,
Ramana

ramanaraoeee
Does anyone here utilize Active Directory groups for email notifications within CA-SCM?

Please give me your advice.

Digital_CB
Can GiT repositories be locked down?

We are in the process of evaluating GiT for our developers to use for source control. We already have CA SCM, but they said it does not branch well so they want to use a different tool just for their development state.

One of the requirements is to lock down the GiT repositories so that each team can only update their code. I'm not seeing a way to do this without giving the developers access to the file system where the code is stored.

We have LDAP and would like to use that so that we don't have to manange security seperately. We would give the team read/write/update access to the folder on the file system, but that would not stop them from updating the code outside of GiT.

Am I missing something?

NPierce

Pages

CMCrossroads is a TechWell community.

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