Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Delivering Change Sets delivers unexpected files

Questions
Tags
Users
Badges
Chris Barlock
(163●4) retagged
Sep 27 '12, 4:53 p.m.
Just a few minutes ago, I had two files with modifications in the Unresolved folder of my Pending Changes view.  I right-clicked on one of them, created a new change set and associated a work item with it.  Then I right-clicked on the change set and did "deliver and resolve work item."  When it finished, the other file was gone from Pending Changes!  I checked the change set associated with the work item -- and there it was, sucked up into the change set.  This is Bad Behavior.  I did not want to deliver that second file.

I'm using the RTC 3.0.4 feature installed into the Eclipse 4.2 Java EE package.

Comments?  Bug?

Chris

1 vote

Comments
Bo Chulindra
JAZZ DEVELOPER Sep 27 '12, 5:54 p.m.
@cbarlock: I opened a new defect Delivering Change Sets delivers unexpected files (234179). Please follow up there.

Chris Barlock
Sep 27 '12, 6:47 p.m.
Thank you, Bo!

2 answers
239 views
1 vote

2 answers

Permanent link
Olivier Thomann
JAZZ DEVELOPER (11●1) Oct 01 '12, 9:47 a.m.
Could you please check your preference in:
Preferences>Team>Jazz Source Control>Default action when delivering while there are unresolved changes?

Please report the value of this option there.

Thanks.

Olivier

1 vote

Comments
Chris Barlock
Oct 01 '12, 9:57 a.m.
It is set to "Check-in and deliver". Chris

Olivier Thomann
JAZZ DEVELOPER Oct 01 '12, 10:04 a.m.
Hi Chris, With the option set up that way, the described behavior looks good to me. The option is set up to make sure that unresolved changes are checked in before delivering the code. Reset the value to : Continue without checkin or Prompt for action and make sure you don't ask to checkin if you don't want your unresolved changes to be checkin and deliver. You can also checkin your unresolved changes in a new change set and only deliver the first one. Hope this help, Olivier

2 votes

Permanent link
Olivier Thomann
JAZZ DEVELOPER (11●1) Oct 02 '12, 2:51 p.m.
Chris,

Could you please confirm that comment 2 helped you to solve your issue?
If this is the case, then the work item 234179 can be closed?
Thanks.

Olivier

0 votes

Comments
Bo Chulindra
JAZZ DEVELOPER Oct 02 '12, 3:09 p.m.
@cbarlock: see above.

Chris Barlock
Oct 02 '12, 3:20 p.m.
Thanks Olivier.  I didn't see your previous email.  Yes, changing the preference to Prompt for action does solve the problem.  I hesitated at the prompt, though.  It asked if I wanted to check in the changes and it wasn't crystal clear if it would check in the unresolved changes if I clicked yes or do nothing if I clicked no.  I clicked no and saw that it checked in the change set and left the unresolved files alone.  I think there is room for improvement in the prompt dialog. That said, 234179 can be closed, unless you want to use it to improve the prompt.  I'll leave that call up to you.

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 2,441

Question asked: Sep 27 '12, 3:02 p.m.

Question was seen: 239 times

Last updated: Oct 02 '12, 3:20 p.m.

Confirmation Cancel Confirm