Baseline confusion
Using RTC 2.0.0.2
I had come to believe that I understood streams, snapshots and baselines
... but I now see that I'm conceptually missing something.
My team uses JBE builds to do all official building. Once a build is
tested, I look at the associated snapshot in the build repository, and I
do one thing .. I "promote" it to the stream. I don't create nor do I
deliver, any baseline's myself.
(actually once, very early in the project I did manually create a
baseline for all components and I delivered it. That's an exception however)
I don't manually create any baselines, and I've always assumed that the
snapshots created by the builds (the ones that I promote) have
baseline's associated with them.
However, when I do a "Show->Baselines" on any of the components in my
stream, I see one, and only one, baseline ... the baseline that I
manually created and delivered long before we were doing automated Jazz
builds. I see no other baseline's, even though the stream itself has
dozens of snapshots.
So, where are the baseline's for all the snapshot's that I've promoted
to the stream ?
A followup question ...
That early baseline that was 'delivered' to the stream has no snapshot
associated with it (I was new!) ... can I now go back and create a new
snapshot associated with that early baseline in each component ?
Not sure if I've explained myself well here .. hope so
Cheers
Dave
I had come to believe that I understood streams, snapshots and baselines
... but I now see that I'm conceptually missing something.
My team uses JBE builds to do all official building. Once a build is
tested, I look at the associated snapshot in the build repository, and I
do one thing .. I "promote" it to the stream. I don't create nor do I
deliver, any baseline's myself.
(actually once, very early in the project I did manually create a
baseline for all components and I delivered it. That's an exception however)
I don't manually create any baselines, and I've always assumed that the
snapshots created by the builds (the ones that I promote) have
baseline's associated with them.
However, when I do a "Show->Baselines" on any of the components in my
stream, I see one, and only one, baseline ... the baseline that I
manually created and delivered long before we were doing automated Jazz
builds. I see no other baseline's, even though the stream itself has
dozens of snapshots.
So, where are the baseline's for all the snapshot's that I've promoted
to the stream ?
A followup question ...
That early baseline that was 'delivered' to the stream has no snapshot
associated with it (I was new!) ... can I now go back and create a new
snapshot associated with that early baseline in each component ?
Not sure if I've explained myself well here .. hope so
Cheers
Dave
18 answers
This is a bug in the documentation.
A snapshot can be associated with either a stream or a workspace, but at
most one at any given time.
I've submitted work item 152567 to get this fixed.
Cheers,
Geoff
On 2/6/2011 7:23 PM, roblogie wrote:
A snapshot can be associated with either a stream or a workspace, but at
most one at any given time.
I've submitted work item 152567 to get this fixed.
Cheers,
Geoff
On 2/6/2011 7:23 PM, roblogie wrote:
Why does the RTC documentation state:
A snapshot can be associated with one or more streams. A snapshot
can be delivered and accepted in the same way as a baseline or change
set
Is this correct ?
Note: I also know of no way to either accept or deliver a snapshot. You
can promote a snapshot, but that is a very different operation from
deliver. You can create a stream or workspace from a snapshot, but that
is not the same as being able to accept a snapshot. I've added that
issue to the description of 152567.
Cheers,
Geoff
On 2/7/2011 1:21 AM, Geoffrey Clemm wrote:
can promote a snapshot, but that is a very different operation from
deliver. You can create a stream or workspace from a snapshot, but that
is not the same as being able to accept a snapshot. I've added that
issue to the description of 152567.
Cheers,
Geoff
On 2/7/2011 1:21 AM, Geoffrey Clemm wrote:
This is a bug in the documentation.
A snapshot can be associated with either a stream or a workspace, but at
most one at any given time.
I've submitted work item 152567 to get this fixed.
Cheers,
Geoff
On 2/6/2011 7:23 PM, roblogie wrote:
Why does the RTC documentation state:
A snapshot can be associated with one or more streams. A snapshot
can be delivered and accepted in the same way as a baseline or change
set
Is this correct ?
relating to the thread "Baseline confusion" and to my own confusion with some strange behaviour i have seen:
I believe it would be extremely helpful to have kind of a conceptual E/R model of all SCM related artefacts (baselines, snapshost, components, change sets, ...) and then define the operations (deliver, promote, accept, ...) in context of this model and its relationships.
I believe it would be extremely helpful to have kind of a conceptual E/R model of all SCM related artefacts (baselines, snapshost, components, change sets, ...) and then define the operations (deliver, promote, accept, ...) in context of this model and its relationships.
relating to the thread "Baseline confusion" and to my own confusion with some strange behaviour i have seen:This article doesn't have a diagram but the last section explains the different parts of source control. You can also create a flow diagram from a stream or workspace that may help visualize how components are used with streams/workspaces and how streams/workspaces flow to each other.
I believe it would be extremely helpful to have kind of a conceptual E/R model of all SCM related artefacts (baselines, snapshost, components, change sets, ...) and then define the operations (deliver, promote, accept, ...) in context of this model and its relationships.
https://jazz.net/library/article/41
relating to the thread "Baseline confusion" and to my own confusion with some strange behaviour i have seen:This article doesn't have a diagram but the last section explains the different parts of source control. You can also create a flow diagram from a stream or workspace that may help visualize how components are used with streams/workspaces and how streams/workspaces flow to each other.
I believe it would be extremely helpful to have kind of a conceptual E/R model of all SCM related artefacts (baselines, snapshost, components, change sets, ...) and then define the operations (deliver, promote, accept, ...) in context of this model and its relationships.
https://jazz.net/library/article/41
i am not looking for flow diagramms, maybe i should have used the term "meta model", i.e. what are the conceptual relationships between the artefacts.
i am not looking for flow diagramms, maybe i should have used the term "meta model", i.e. what are the conceptual relationships between the artefacts.I was hoping the article would help out more than the flow diagram even though it doesn't have any visual model. I only mentioned the flow diagram because it can show the components contained in streams/workspaces. It shows that change sets flow between streams/workspaces, which means deliver/accept are operations on change sets (baselines can be delivered too because it's an immutable set of changes up to a point in the history).
I would recommend going through the JUnit tutorial to get a hands on feel for what the artifacts mean.
I've been hearing this kind of thing from a lot of customers, so I've
posted a set of work-items:
168380: Model for SCM artifacts (this request)
168379: Model for all RTC artifacts (generalizing this request for all
of RTC)
If you are interested in these models, please post a comment to the
appropriate work item, indicating what parts of these models are most
important to you.
I will also be pushing for an even further generalization of this
request to all CLM products (i.e. including RRC and RQM), and all
Rational team products (i.e. including ClearCase, ClearQuest, Synergy,
Change, DOORS, Focal Point, etc.), but that is beyond the scope of this
forum.
Cheers,
Geoff
On 6/3/2011 10:38 AM, lothar wrote:
posted a set of work-items:
168380: Model for SCM artifacts (this request)
168379: Model for all RTC artifacts (generalizing this request for all
of RTC)
If you are interested in these models, please post a comment to the
appropriate work item, indicating what parts of these models are most
important to you.
I will also be pushing for an even further generalization of this
request to all CLM products (i.e. including RRC and RQM), and all
Rational team products (i.e. including ClearCase, ClearQuest, Synergy,
Change, DOORS, Focal Point, etc.), but that is beyond the scope of this
forum.
Cheers,
Geoff
On 6/3/2011 10:38 AM, lothar wrote:
I believe it would be extremely helpful to have kind of a conceptual
E/R model of all SCM related artefacts (baselines, snapshost,
components, change sets, ...) and then define the operations
(deliver, promote, accept, ...) in context of this model and its
relationships.
Just for the record, the terminology in your original request was
correct (:-) ... you were looking for a model of the data (as opposed to
the data itself, which is what is shown in the flow diagrams).
Cheers,
Geoff
On 6/3/2011 12:23 PM, lothar wrote:
correct (:-) ... you were looking for a model of the data (as opposed to
the data itself, which is what is shown in the flow diagrams).
Cheers,
Geoff
lothar wrote:
I believe it would be extremely helpful to have kind of a conceptual
E/R model of all SCM related artefacts (baselines, snapshost,
components, change sets, ...) and then define the operations
(deliver, promote, accept, ...) in context of this model and its
relationships.
tmokwrote:
This article doesn't have a diagram but the last
section explains the different parts of source control. You can also
create a flow diagram from a stream or workspace that may help
visualize how components are used with streams/workspaces and how
streams/workspaces flow to each other.
https://jazz.net/library/article/41
On 6/3/2011 12:23 PM, lothar wrote:
i am not looking for flow diagramms, maybe i should have used the term
"meta model", i.e. what are the conceptual relationships
between the artefacts.
page 2of 1 pagesof 2 pages