How to get ClearCase stream name by a given view path?
You can take advantage of the -cview
option of the lsstream
command:
cleartool lsstream -cview
With fmt_ccase:
cleartool lsstream -fmt "%n" -cview
I like to see where this stream is located within a project, so I usually do a:
cleartool lsstream -cview -anc
How to retrieve stream name by a given view name in ClearCase UCM?
By script:
cleartool lsstream -view view_tag
See cleartool lsstream
man page:
–vie/w view-tag
Displays information for the stream connected to the specified view.
How to retrieve the integration-stream that belongs to my development view
You could use a fmt_ccase
query with cleartool describe
, by looking at the UCM project:
cleartool descr -fmt "%[istream]Xp" project:myProject@\myPVob
If you don't have the project name ready, you can:
- get the stream from your view
- list all pvobs and find the one which includes said dev stream: the current project will be your project name, from which you can get the integration stream name.
How to list branches associated with a view in clearcase
No: only an UCM view has an associated branch (through its stream).
See "How to obtain UCM stream and baseline with cleartool
?" or "How to get ClearCase stream name by a given view path?"
cleartool lsstream -fmt "%n" -cview
A non-UCM view would have any selection rules you want in its config spec.
You need to do a cleartool lsvtree /path/to/a/file
(add --graph
for the graphical view) in order to see its versions and the branches involved.
working in /vobs/some/path versus /view/view-tag-name/vobs/some/path
what's the difference between working in
/vobs/some/path
in asetview
shell versus working in/view/view-tag-name/vobs/some/path
in a plain shell?
Do not use cleartool setview
: As I explained before, the cleartool setview
command opens a subshell in which commands are supposed to be run, which can be problematic.
Working in /view/view-tag-name/vobs/some/path
means you remain in your main shell, with all its properties.
what is the proper term to use when referring to the
/view/view-tag-name
directory?
That references the full path view root folder (inside which you are mounting vobs and accessing versions based on the view config spec and its selection rules)
In /vobs/some/path
, you can still see the view you are in with cleartool pwv ("path working view").
why when I do
ct lsview -l -properties -ful view-tag-name
I don't see any reference to the/view/view-tag-name
directory?
You are seeing the property of the view, which will then be mounted in /view/view-tag-name
(on Unix) or M:\view-tag-name
on Windows.
Those properties make no assumption on the runtime usage of that view, they only display static metadata (like the view storage or the view type)
command to identify the clearcase ucm view which is out of sync from stream?
Thanks VonC.
The below method is failed (stream config spec and view config spec is not in order sometimes).
cleartool catcs will return some uuid which we cannot compare with foundation baselines.
I have achieved this by comparing cleartool dump -l <streamname>
output with cleartool catcs
output.
Found the another method.
The ucmutil command ucmutil lspvar -pvar SUM_CSPEC_ID <streamname>
will return the config_spec_id of the stream which can be compared with cleartool catcs | grep -i identity
output. The config_spec_id is mentioned in view config spec as identity UCM.Stream oid:uuid@vobuuid:uuid config_spec_id in the second line.
Related Topics
Restoring Stdout and Stderr to Default Value
Which Is the Best Way to Make Config Changes in Conf Files in Ansible
How to Join Multiple PDF Pages to a Single Page
Set Environment Variables for Non-Interactive Shell
.Zshrc Config File Syntax Error
Sudoers Nopasswd: Sudo: No Tty Present and No Askpass Program Specified
How to Print a Number in Arm Assembly
Chef Chef-Validator.Pem Security
Linux Get Process Name from Pid Within Kernel
No Error on Xcb_Grab_Key But Event Loop Not Catching (Global Hotkey)
Ldconfig Only Links Files Starting with Lib*
How Many Instructions Does Linux Kernel Need in Order to Handle an Interrupt on an Arm Cortex A9
Fatal: Git Was Built Without Support for Git-Add--Interactive (No_Perl=1)
Why /Lib32/Libc.So.6 Has Two "Fopen" Symbol in It