clearcase

Delete file from ClearCase checked out on another branch

孤街浪徒 提交于 2019-11-30 19:43:24
问题 I am trying to delete a file in ClearCase. When I attempt to delete it I get a message that the element has checkouts. When I do a version tree on the file I see that the file is checked out by another user, in another view, on a different branch. How do I delete this file? In addition why doesn't ClearCase let me delete this file? 回答1: You can delete it through the command line and cleartool, by forcing its delete (option which isn't available with the GUI) cleartool rmname -force theFile

How to update clearcase view via windows command line?

核能气质少年 提交于 2019-11-30 19:39:16
I have a view named "Dev_view" in ClearCase and want to update the view via windows command line. Is there a way to do that? In particular, what other command can trigger a view update? VonC See cleartool update command (for full ClearCase client, not for CCRC) cd /path/of/your/snapshot/view cleartool update . You cal also add the following options: -ove/rwrite Overwrites all hijacked files with the version selected by the config spec. -nov/erwrite Leaves all hijacked files in the view with their current modifications. -ren/ame/ Renames hijacked files to filename.keep and copies the version in

Not getting the coverage on new code in sonar dashboard

半腔热情 提交于 2019-11-30 18:17:32
问题 I am trying to use scm activity plugin 1.8 for clearcase and using sonar 4.3.3 and got the blame information in the sonar but did not getting the coverage on new code in dashboard 回答1: You should add Code Coverage Tool to your build process. If you use Maven, then you can add: <build> ... <plugins> ... <plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <version>0.7.5.201505241946</version> <executions> <execution> <id>jacoco-initialize</id> <goals> <goal

How best to branch in Clearcase?

社会主义新天地 提交于 2019-11-30 18:13:06
问题 I've previously documented my opinions on Clearcase as a source control system, but unfortunately I am still using it. So I turn to you guys to help me alleviate one of my frustrations. We have just moved from a one-branch-per-developer system, to a one-branch-per-task in an attempt to improve some of the issues that we've been having with determining why certain files were changed. Generally I am happy with the solution, but there is one major issue. We are using simple scripts to start and

Toward an ideal workflow with ClearCase and Git

断了今生、忘了曾经 提交于 2019-11-30 16:00:33
问题 Introduction This is more than a fact, using ClearCase (not UCM) as main SCM for large projects maintained by few people is a pretty not efficient solution. When it's Corporate Standard, we are stuck with it and we need to find an efficient workaround. The usual workflow with ClearCase consists of a master branch, a develop branch and several new feature branches. o--------o (feature) / \ ----o--o---o-----o----o (develop) / \ \ *----------o---------o (main) Example Actually, what I call a

Toward an ideal workflow with ClearCase and Git

社会主义新天地 提交于 2019-11-30 15:51:38
Introduction This is more than a fact, using ClearCase (not UCM) as main SCM for large projects maintained by few people is a pretty not efficient solution. When it's Corporate Standard, we are stuck with it and we need to find an efficient workaround. The usual workflow with ClearCase consists of a master branch, a develop branch and several new feature branches. o--------o (feature) / \ ----o--o---o-----o----o (develop) / \ \ *----------o---------o (main) Example Actually, what I call a feature could be also a simple refactoring, such as a massive renaming inside the project. In this example

how to find all the branch type created by one person in clearcase

拟墨画扇 提交于 2019-11-30 15:34:20
问题 I created a branch type one month ago , but for some reason delayed to use it until now. But now I just have a vague memory of the branch name but not very sure about it . So I'm wondering if clearcase has the feature that list all the branch type create by a person, in my case just me, then I can find the exact name of the branch type I created one month ago . Need your help, thanks in advance . 回答1: You can list the brtype of a vob, displaying only what you need with fmt_ccase directives:

how to find all the branch type created by one person in clearcase

余生长醉 提交于 2019-11-30 14:32:51
I created a branch type one month ago , but for some reason delayed to use it until now. But now I just have a vague memory of the branch name but not very sure about it . So I'm wondering if clearcase has the feature that list all the branch type create by a person, in my case just me, then I can find the exact name of the branch type I created one month ago . Need your help, thanks in advance . You can list the brtype of a vob, displaying only what you need with fmt_ccase directives: cleartool lstype -kind brtype -invob \myVob would be enough to do some grep, but for a more compact output:

ClearCase vs. Git version control [closed]

那年仲夏 提交于 2019-11-30 11:48:52
问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 3 years ago . We are using a multisite ClearCase repository, and often we require to merge and build our system. This merge and replication takes almost three days to be available across sites. Hence to be more efficient, we are planning to move to Git version control. Could you please

Clearcase issue while “add file to source control”

我的未来我决定 提交于 2019-11-30 09:04:24
问题 I am facing a following issue while adding a file to clearcase (UCM) --------------------------- Rational ClearCase Explorer --------------------------- Error adding 'M:\Myviename\Myvob\Myproj\Implementation\DataSource\Deployment\BOM\SupportFiles\Service.config' to source control. Created branch "Tm6-Proj-Dev2" from M:\Myviename\Myvob\Myproj\Implementation\DataSource\Deployment\BOM\SupportFiles\Service.config' version "\main\0". Type manager "text_file_delta" failed create_version operation.