Knowing SCM elements UUIDs from UI

The UUIDs are intentionally hidden in the Eclipse rich client. They're
intended to be implementation details (and we don't want to overwhelm
users with long random uuids) but they are exposed in the command line
client so that automated build engines can uniquely identify things.

Is there a particular reason why you want to know what UUIDs are in the
rich client?

On Thu, 12 Nov 2009 04:30:38 -0500, Chemi <jmordax> wrote:

SCM CLI can manage SCM elements referenciated by its UUID.
My question is, is tehre any way to know the UUID of a specific element
like a changeSet or a Stream form the UI (Eclipse client)? I haven't
found a way.

Thanks,

Chemi.

--

On 13-Nov-09 5:14 PM, Andrew Hoo wrote:

The UUIDs are intentionally hidden in the Eclipse rich client. They're
intended to be implementation details (and we don't want to overwhelm
users with long random uuids) but they are exposed in the command line
client so that automated build engines can uniquely identify things.

Is there a particular reason why you want to know what UUIDs are in the
rich client?

I was playing around with scm deliver command, and I didn't know how to
see the UUID or name of a ChangeSet to test the command.

if you're using the command line, the aliases are printed as 4 digit
numbers that you can use to identify recently cached items.
Usually places that ask for a name accept: Aliases, UUIDS, or "some string
name that we hope is unique". For change sets, this is the comment
entered for the change set.

The 4 digit aliases are not perminantely stable (but enough to make it
useable for human command line users)

For a build script though, you will want to specify "lscm --show_uuid yes
--show-alias no" to make it possible to parse the uuids.


On Wed, 18 Nov 2009 00:15:06 -0500, Chemi <jmordax> wrote:

On 13-Nov-09 5:14 PM, Andrew Hoo wrote:
The UUIDs are intentionally hidden in the Eclipse rich client. They're
intended to be implementation details (and we don't want to overwhelm
users with long random uuids) but they are exposed in the command line
client so that automated build engines can uniquely identify things.

Is there a particular reason why you want to know what UUIDs are in the
rich client?

I was playing around with scm deliver command, and I didn't know how to
see the UUID or name of a ChangeSet to test the command.

As Andrew mentions, in normal operation of the SCM CLI you should not need to know the UUIDs.

But sometimes you really do need to get the UUID, and they're available for some items if you know where to look. E.g. try actions like Properties, Copy URL, etc. Or browse the item in the web UI and look at the XHRs going by in Firebug ;-).