RTC Command Line and Listing Components
I am trying to list the components under my workspace with the command line (using RTC 3.0 fix 1). But I can't get it to use the correct user name to login as.
Listing workspaces works fine:
But when I list the components, it totally ignores the -u/--username option:
I have tried changing the order of the options, using --username instead of -u, etc. It always ignores the option. I went to my laptop and tried it, and I'm getting the same results. The thing is, it worked for me before, because this is the only way I know to get the UUIDs for the components of a workspace. And I don't think I've updated the software on either machine. Is this a known bug? Is there some other way (using the UI, maybe) to get the UUIDs? |
4 answers
The problem with the UUIDs is that I thought they were session-specific. In other words, what the UUIDs are from one machine do not match what they are from a different machine. A single workspace, for instance, has a different UUID on my laptop than it does on my Linux machine in our lab. And I thought I read somewhere that the UUIDs could even change on the same machine. But that's still good info to know how to do that, thanks! That's actually not the case. UUIDs are set in stone on the Jazz repository, and do no change from machine to machine. A UUID for a repository workspace 'A' will always have the same UUID regardless of which machine you are logged on to. (same with streams / components). Unless you are talking about different repository workspaces that you use on each machine, then each one will have a different UUID (and name usually). The one thing that 'does' appear to change for example may be the current 'state' of a file. A Jazz shared file has a fixed UUID to identify itself (which will never change), but it also has a UUID to represent the current state; and so the history of certain artifacts on the Jazz repository could have a list of UUIDs representing each state as it changed over time. |
|
The problem with the UUIDs is that I thought they were session-specific. In other words, what the UUIDs are from one machine do not match what they are from a different machine. A single workspace, for instance, has a different UUID on my laptop than it does on my Linux machine in our lab. And I thought I read somewhere that the UUIDs could even change on the same machine. But that's still good info to know how to do that, thanks!
|
this is the only way I know to get the UUIDs for the components of a workspace. Is there some other way (using the UI, maybe) to get the UUIDs? Not sure what the issue is in that case, but you could use the Web UI I think to find the UUIDS. When looking in a component, you should see the UUID of that component in the URL... |
Maybe try creating a login session and using that, ie
lscm login -r https://csnext.myco.com/ccm6/ -u dlwester@myco.com -n mySession Then use the mySession nickname in any future lscm command, ie lscm list components -r mySession I am trying to list the components under my workspace with the command line (using RTC 3.0 fix 1). But I can't get it to use the correct user name to login as. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.