Base line to revert back.
I've tried looking back at some of the posts here regarding baseline/snaphot and still not certain about it.
Basically what I'm looking to do is to take a baseline/snapshot of my current (local/private) workspace with all its changes. Then accept a large number of incoming change sets. If I determine that there is an issue (build breaks) from these changes I would like to revert back on my local/private workspace to state the source was in when I took baseline/snapshot
Is this possible ? If so I haven't quite figured it out
Thanks.
Basically what I'm looking to do is to take a baseline/snapshot of my current (local/private) workspace with all its changes. Then accept a large number of incoming change sets. If I determine that there is an issue (build breaks) from these changes I would like to revert back on my local/private workspace to state the source was in when I took baseline/snapshot
Is this possible ? If so I haven't quite figured it out
Thanks.
6 answers
Correct ... delivering the baseline to the stream does not revert the
stream to that baseline, it just adds that baseline to the "history" of
the stream. But I agree that this "revert" semantics would be a
reasonable interpretation of the baseline-deliver action. I've added
this as a comment to workitem 72766.
Cheers,
Geoff
rineholt wrote:
stream to that baseline, it just adds that baseline to the "history" of
the stream. But I agree that this "revert" semantics would be a
reasonable interpretation of the baseline-deliver action. I've added
this as a comment to workitem 72766.
Cheers,
Geoff
rineholt wrote:
gmclemmwrote:
The reason to deliver a baseline is so that it becomes visible in the
history of the stream to which you are delivering it.
But I agree that you should have the option to drop it, rather than
being required to deliver it. I've submitted workitem 72766 for
this.
In general, I believe you cannot do any harm by delivering a
baseline.
I *assumed* delivering the baseline to the stream would revert the
stream to the baseline. hmm I'm guessing not now; is that right?
Right-click on your workspace in the Pending Changes view,
select Replace-With -> Snapshot
select the snapshot you created.
And you are done.
Cheers,
Geoff
rineholt wrote:
select Replace-With -> Snapshot
select the snapshot you created.
And you are done.
Cheers,
Geoff
rineholt wrote:
I've tried looking back at some of the posts here regarding
baseline/snaphot and still not certain about it.
Basically what I'm looking to do is to take a baseline/snapshot of my
current (local/private) workspace with all its changes. Then accept
a large number of incoming change sets. If I determine that there
is an issue (build breaks) from these changes I would like to revert
back on my local/private workspace to state the source was in when I
took baseline/snapshot
Is this possible ? If so I haven't quite figured it out
Thanks.
Right-click on your workspace in the Pending Changes view,
select Replace-With -> Snapshot
select the snapshot you created.
And you are done.
Cheers,
Geoff
rineholt wrote:
I've tried looking back at some of the posts here regarding
baseline/snaphot and still not certain about it.
Basically what I'm looking to do is to take a baseline/snapshot of my
current (local/private) workspace with all its changes. Then accept
a large number of incoming change sets. If I determine that there
is an issue (build breaks) from these changes I would like to revert
back on my local/private workspace to state the source was in when I
took baseline/snapshot
Is this possible ? If so I haven't quite figured it out
Thanks.
I was trying to use baseline. Real novice RTC user here. I haven't' fully tried it out but I see now the mechanics of how to do it.
Thanks!
What has me still confused that both creating a snapshot and baseline in my private workspace I don't see an option to just get rid of it. When I right click on it, change pending view, it gives me an option to ONLY deliver it. Why would I want to delivery a baseline/snapshot? Seems risqu to me.
The reason to deliver a baseline is so that it becomes visible in the
history of the stream to which you are delivering it.
Why do you think it would be risky to deliver it? (People can just
ignore it, if they're not interested in it).
But I agree that you should have the option to drop it, rather than
being required to deliver it. I've submitted workitem 72766 for this.
In general, I believe you cannot do any harm by delivering a baseline.
But baseline flow can be a bit mysterious (to me, anyway :-). For
example, if I create a baseline, it appears on my outgoing changes list,
but then if I accept changes for that component, that outgoing baseline
will disappear from my outgoing changes list (even though that baseline
has not in fact been delivered). Perhaps someone from the SCM team can
comment on the semantics of baseline flowing in and out of a workspace?
Cheers,
Geoff
rineholt wrote:
history of the stream to which you are delivering it.
Why do you think it would be risky to deliver it? (People can just
ignore it, if they're not interested in it).
But I agree that you should have the option to drop it, rather than
being required to deliver it. I've submitted workitem 72766 for this.
In general, I believe you cannot do any harm by delivering a baseline.
But baseline flow can be a bit mysterious (to me, anyway :-). For
example, if I create a baseline, it appears on my outgoing changes list,
but then if I accept changes for that component, that outgoing baseline
will disappear from my outgoing changes list (even though that baseline
has not in fact been delivered). Perhaps someone from the SCM team can
comment on the semantics of baseline flowing in and out of a workspace?
Cheers,
Geoff
rineholt wrote:
What has me still confused that both creating a snapshot and baseline
in my private workspace I don't see an option to just get rid of it.
When I right click on it, change pending view, it gives me an option
to ONLY deliver it. Why would I want to delivery a
baseline/snapshot? Seems risqu to me.
The reason to deliver a baseline is so that it becomes visible in the
history of the stream to which you are delivering it.
Why do you think it would be risky to deliver it? (People can just
ignore it, if they're not interested in it).
But I agree that you should have the option to drop it, rather than
being required to deliver it. I've submitted workitem 72766 for this.
In general, I believe you cannot do any harm by delivering a baseline.
But baseline flow can be a bit mysterious (to me, anyway :-). For
example, if I create a baseline, it appears on my outgoing changes list,
but then if I accept changes for that component, that outgoing baseline
will disappear from my outgoing changes list (even though that baseline
has not in fact been delivered). Perhaps someone from the SCM team can
comment on the semantics of baseline flowing in and out of a workspace?
Cheers,
Geoff
rineholt wrote:
What has me still confused that both creating a snapshot and baseline
in my private workspace I don't see an option to just get rid of it.
When I right click on it, change pending view, it gives me an option
to ONLY deliver it. Why would I want to delivery a
baseline/snapshot? Seems risqu to me.
I *assumed* delivering the baseline to the stream would revert the stream to the baseline. hmm I'm guessing not now; is that right?