It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,880
×12,005
×7,474

question asked: Oct 16 '12, 3:04 a.m.
question was seen: 5,194 times
last updated: Aug 16 '18, 10:17 p.m.

Related questions

Split a Changeset.

0
1
erling jorgensen (40●9●11) | asked Oct 16 '12, 3:04 a.m.
 Hi
Is possible to split a Changeset after it is delivered? As an example move a single file from one changeset to another changeset.

Regards 

Erling

Accepted answer

1
permanent link
Lauren Hayward Schaefer (3.3k●1●17●27) | answered Oct 16 '12, 7:06 a.m.
JAZZ DEVELOPER
Hi Erling,
It is not currently possible to split a changeset after it has been delivered.  An enhancement request is tracking this:  Allow moving changes out of a delivered change set (59688).  You can add a comment to the work item adding your specific use case or support of the enhancement.
erling jorgensen selected this answer as the correct answer
Comments
erling jorgensen commented Oct 16 '12, 8:36 a.m.

Hi Laureen

Thank you. I have added a comment to the workitem and hope it can speed it up. As far as I can see the item is rather old (meaning low-prioritized).

Just to be sure: It isn't possible to do the changeset split programatically?

Lauren Hayward Schaefer commented Oct 16 '12, 8:48 a.m.
JAZZ DEVELOPER

Hi Erling,
A similar forum post from a few months ago discussed the same issue: https://jazz.net/forum/questions/83427/how-do-you-split-out-part-of-a-completed-change-set-into-a-separate-change-set.  I don't know of a way to split the changeset programatically but maybe someone else does.

Geoffrey Clemm commented Oct 16 '12, 8:50 a.m. | edited Aug 16 '18, 10:13 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

That is correct ... it isn't possible to split a change set if it has been completed (programatically or otherwise).   Note that you can of course create a couple of new change sets, and have each change set contain the subset of changes that you want.   But from RTC's point of view, these two new change sets will have no relationship to the original change set.   (You can use the "patch" mechanism to help you create those two new change sets).

erling jorgensen commented Oct 16 '12, 4:21 p.m.

Okay. We are now working on a solution where we split the changesets before delivery into change sets containing each only one change. In this way a split will never come into question, and it is possible freely to pick changes for promotion into production.


Is that solution OK? Will it kill performance or something else?  

Geoffrey Clemm commented Oct 16 '12, 8:12 p.m. | edited Aug 16 '18, 10:16 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

It won't necessarily kill performance, but depending on how many changes are in the change set, it can harm performance.   If your change sets usually have two changes, then splitting them all should be fine.   If your change sets usually have 30 changes, splitting every change set into 30 change sets is likely to have a noticeable effect on the performance of some operations.

Your answer

Register or to post 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.