Recent Q&A Activity

There are those on my team that think a CR is only needed for requirement changes/customer requests and not for defects.

Can someone please help me to explain why this is not true.

I feel that outside of normal help desk support, all changes, to include correction of functional defects should pass through a CR. This way we properly document that a change was necessary to make the system function properly. This also allows us to track items that were not properly addressed during initial development.

Need to find an improved SCM solution for the following scenario:

- application is developed by four developers
- currently have 8 customers
- we have a DEV, TEST, QA, and PROD environment set up for each customer internally (roughly 30-40 total environments, each with it's own DB instance)

Does anyone have any idea why I am getting the below error while executing MKS query?

Cannot show view information: Your query was stopped because it was using too may system resources.

The below ant script is running successfully until yesterday using Harvest 7:

C:\Program Files\CA\SCM\hco.exe" -pn 'Check Out - Read Only' -b '${application.harvest.broker}' -ced -usr '${application.harvest.userId}' -pw '${application.harvest.password}' -en '${application.harvest.environment}' -st '${application.harvest.state}' -vp '${application.harvest.projectdir}' -r -op '${application.harvest.pc}' -sy -cp '${application.checkedout.src}' -s '${application.harvest.filepattern}

I have years of experience in deploying custom web applications. I have developed a build process that is repeatable for building and deploying custom web applications to the development, test, and production environments. Lately, i have been involved in some of our SharePoint projects.

I am getting below error while installing Clearcase through installation manager. This is the command I ran:

./../IM_lnx_1.5/installc input /tmp/temp_response_file -acceptLicense -svp

It fails with below error:

I have a stated record type of Escalation which has a parent/child relationship with a stateless record type of CodeStreams. CodeStreams has a resolution field for each child CodeStream. There can be many CodeStreams to one escalation.

I am trying to create a query that will only return records in which none of the children have a resolution of "fixed".

I have tried a variety of and/or options to no avail, seems some records still come back where a child is "fixed". I am thinking this may have to be done with SQL, any help would be much appreciated.

Can so someone share you the way to implement email submission in 5.2?

I am also using 5.2 and one of our project requested to implement this feature. May be I can make some improvement and share with you.

My supervisor used to have the CM function near the top of the hierarchy along with QA and Test to showcase how our functions touches may touch everyone on the project.

Recently, she moved CM to under Production.

I think this is a huge mistake because CM is much more than just processing CRs and creating release notes. I feel as though the CM role is being minimized for whatever reason. I plan on having a meeting with her to discuss why CM should not be placed under Productions.

Can anyone help in coming up with some points?

We have just upgraded to Dimensions v12.2 and we have found a couple of issues. Has anyone else experienced the same thing? I've created cases with Serena support already but have not received solutions yet.

1. In Windows Explorer we cannot copy files from another location into our work areas. We receive a message the files in the work area cannot be overwritten. This is a problem for developers who make code changes outside of the work area and then copy them into the work area before delivery.

--- Context:
Conflicting merges must be solved by developers.
All developers are part of the same company on several sites.
A merge leads to a lot of conflicts involving several developers (for ex. During N -> N+1 synchronization while N and N+1 project versions are running in the same repository)

--- Here is my solution:
• All the conflicts are managed in a clone, merging_clone
• This clone is shared at OS level
• Developers of remote sites can connect to a local LAN Git machine to access merging_clone

Pages

CMCrossroads is a TechWell community.

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