CODEWITHSUNDEEP
rtc
blue-sky
blue-sky

Reputation: 53826

Why does RTC source control attempt to force me to deliver change sets?

When checking in & delivering files I receive this message :

enter image description here

I do not want to deliver other change sets as part of this delivery of files ? Is there a reason RTC source control does this, how can it be prevented ?

Upvotes: 1

Views: 502

Answers (1)

VonC
VonC

Reputation: 1325137

I usually avoid and don't recommend the "check-in and deliver" option, especially since it will "complete" the change set and force the developer to create a new change set at the next check-in.
That means I ended up with tons of change sets delivered by developer unaware of this "feature".

To control what is delivered, it is best to check in, and then deliver.

That thread mentions a situation similar to yours:

The UI allows to select a change set and just check in and deliver this specific change set.
The controlling element is where you right click the outgoing changes.

  • If you right click a single change set you deliver just that.
  • If you right-click on outgoing you deliver all change sets

I suspect from your description what happened is, there where several outgoing changes locally that needed check in.
The user selected the unresolved node and selected "check-in and deliver".
The result is that the changes where subsumed into a new change set and delivered.

Upvotes: 1

Related Questions