Use Case for suspending a change set
I am presenting the concept of reserving and suspending change sets to group next week. Does anybody have any use cases for suspending change sets. I see one, that is a developer is working on a new feature. The development manager contacts him and says "stop working on that feature because we need to address an issue more pertinent." The developer can suspend the change set in order to work on it at a later date. Is the use case? Are there any others?
|
Accepted answer
It's also used when you're working on one computer and have to resume work on a different computer. Some developers do this if they are developing on different platforms or want to work at home. Using the same repository workspace in this case is not recommended and the only way to bring an open change set to another repository workspace is to use suspend/resume.
Suspend is also available from the "Submit for Review" action in Pending Changes. When a developer is working on a task, he can submit his change set for review in a work item. When going through this work flow, suspending the change sets is an option when creating the work item approval. This allows the developer to continue working on something else while waiting for approval before he is allowed to deliver. Sean Burke selected this answer as the correct answer
|
One other answer
Jared Burns (4.5k●2●9)
| answered Feb 07 '14, 6:33 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
We also use this in our day-to-day for the developer who's responsible for baselining our team stream and promoting the team's work to the integration stream. That developer (who we call the Buildmeister) will suspend any of their in-progress work, smoke test and baseline the latest from the stream, and then deliver the team's baselines to integration before finally resuming their work.
|
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.