How to identify a reversed changeset in scm compare
Hi,
Here is a scenario:
Developers deliver their changesets to the stream, Say 30 changesets have been delivered so far. Now, two of them have delivered a wrong fix. A backout has to be done for the wrong fix. Reverse changeset option is being used and the code backout is completed. Old workitem is removed and a new one is associated with the patch to deliver the patch.
Now, when we take reports using compare commands, we get the list of all changesets/workitems delivered, here in this case, two of them are really not valid in terms of a fix. They are only backout workitems and do not add any value in terms of source code functionality.
We have few automated scripts in place.My question is, how will i get my script to identify the reversed changeset ? Is it possible to apply a label on successful reversal of changeset ? Or, to list only the changesets that are not due to reversal operation ?
Any suggestions on handling this scenario are welcome
Regards,
Pavithra
Here is a scenario:
Developers deliver their changesets to the stream, Say 30 changesets have been delivered so far. Now, two of them have delivered a wrong fix. A backout has to be done for the wrong fix. Reverse changeset option is being used and the code backout is completed. Old workitem is removed and a new one is associated with the patch to deliver the patch.
Now, when we take reports using compare commands, we get the list of all changesets/workitems delivered, here in this case, two of them are really not valid in terms of a fix. They are only backout workitems and do not add any value in terms of source code functionality.
We have few automated scripts in place.My question is, how will i get my script to identify the reversed changeset ? Is it possible to apply a label on successful reversal of changeset ? Or, to list only the changesets that are not due to reversal operation ?
Any suggestions on handling this scenario are welcome
Regards,
Pavithra
2 answers
The only mechanism I am aware of is the manual approach of adding a
standard prefix to the comment of the change set when you checkin the
reversal patch (that's what I do).
I've submitted work item 173309 to get some automated support for this.
Cheers,
Geoff
On 8/5/2011 4:08 AM, prangan wrote:
standard prefix to the comment of the change set when you checkin the
reversal patch (that's what I do).
I've submitted work item 173309 to get some automated support for this.
Cheers,
Geoff
On 8/5/2011 4:08 AM, prangan wrote:
Hi,
Here is a scenario:
Developers deliver their changesets to the stream, Say 30 changesets
have been delivered so far. Now, two of them have delivered a wrong
fix. A backout has to be done for the wrong fix. Reverse changeset
option is being used and the code backout is completed. Old workitem
is removed and a new one is associated with the patch to deliver the
patch.
Now, when we take reports using compare commands, we get the list of
all changesets/workitems delivered, here in this case, two of them
are really not valid in terms of a fix. They are only backout
workitems and do not add any value in terms of source code
functionality.
We have few automated scripts in place.My question is, how will i get
my script to identify the reversed changeset ? Is it possible to
apply a label on successful reversal of changeset ? Or, to list only
the changesets that are not due to reversal operation ?
Any suggestions on handling this scenario are welcome
Regards,
Pavithra