delivery doen't affect loaded baseline-name
![]()
Hi,
I loaded a workspace based on a baseline. In that local workspace I did some changes and delivered the work into the repository workspace. The component in that repository workspace now contains the changed sources. However, the baselinename didn't change and there is no indication that it's not equal anymore to that version... (!) Regards, Bernd. |
2 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 28 '09, 10:26 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
First, note that the content (set of versions and change sets) in a
baseline is immutable ... once a baseline is created, its content cannot be changed. From a terminology perspective, it is likely that you "checked in" your changes to your repository workspace, as opposed to "delivering" it. Two places you look to see if the content of your repository workspace has "changed" is the history view or the pending changes view. The history view will show you whether new change-sets have been added. The pending changes view will show you whether the content of your repository workspace has changed wrt your team stream. Cheers, Geoff berndyman wrote: Hi, |
![]()
To further expand on what Geoff has said, once you have checked in your
changes into the repository workspace, they do not affect the immutable baseline that is already in your component. Rather your new changes 'sit ontop' of that previous baseline. If your workspace has a flow target to a stream, then you will see the outgoing changes that you can deliver to. That would be your indication that what you have in your repository workspace is different from what is currently in that stream. On Tue, 28 Jul 2009 10:08:01 -0400, berndyman <bvo> wrote: Hi, -- |
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.