How to get stream history via CLI?
I'm trying to obtain the history of a stream via the CLI. It seems that the scm history command wants you to specify both a workspace and component. Is there a way to specify an entire stream so that I can obtain the history of deliver operation from *all* developers on my team who have delivered changes to the stream? The history documentation states that the -w option is the workspace or stream but when I try to specify a stream name (hoping to pick up the history of all components that are part of that stream) I get:
If I also specify a component with the -c option I get a history of *my* commits for that component which isn't all that interesting since I want to see other developers' commits too.
If I may speak SVN for a moment, what I really want is something equivalent to:
svn log -r { DATE1:DATE2 } what will allow me to build a utility around the scm history command (I'm trying to create a commit e-mail notifier that obtains its info from periodic polling using the scm history command).
scm history -w"<stream>"
Problem running 'history':
CWD must be descendant of CFA root.
If I also specify a component with the -c option I get a history of *my* commits for that component which isn't all that interesting since I want to see other developers' commits too.
If I may speak SVN for a moment, what I really want is something equivalent to:
svn log -r { DATE1:DATE2 } what will allow me to build a utility around the scm history command (I'm trying to create a commit e-mail notifier that obtains its info from periodic polling using the scm history command).
11 answers
Something else to clarify ... the history view in the Eclipse GUI shows
you every change set (commit) that has occurred in any component in any
stream or workspace. If the command line currently only allows you to
see your own change sets (commits), then that is a limitation of the
command line (please submit an enhancement request), and not a
limitation of the RTC model.
Cheers,
Geoff
On 2/15/2011 4:08 PM, stus wrote:
you every change set (commit) that has occurred in any component in any
stream or workspace. If the command line currently only allows you to
see your own change sets (commits), then that is a limitation of the
command line (please submit an enhancement request), and not a
limitation of the RTC model.
Cheers,
Geoff
On 2/15/2011 4:08 PM, stus wrote:
It was clear, thanks. My only concern with the snapshot concept is
that it requires that either one be be created manually (you can't
always be sure people will) or that a formal build is generated (so
that it's created as part of that.) I can think of many instances
where those two things won't happen but yet I still want to track all
changes over some defined time period. Years ago we tried to track
commit points with CVS tags and it was a disaster (precisely because
they were somewhat arbitrary and we ended up with 100s of them that
soon became meaningless.) In that way, the SVN concept of an atomic
commit with a well-defined repository state (defined by an integer)
was a god send.
page 2of 1 pagesof 2 pages