Swarm 2014.1: User Guide

How do I get a local copy of the review's code for evaluation?

Swarm manages one or more changelists containing shelved copies of all of the files belonging to a specific review. You can unshelve the files to receive a copy of the review’s code.

Determine the changelist containing the review's files

  1. Visit the review's page.

  2. The current review version's changelist appears in the file list heading:

    A pre-commit review's changelist in the file list heading

    In this example, the changelist is 697707. You use the identified changelist in place of shelved changelist below.

Note

Swarm can version file updates in reviews. For more information, see “Review display”.

Using P4

For a shelved changelist, use a command-line shell and type:

$ p4 unshelve -c shelved changelist

For a committed changelist, use a command-line shell and type:

$ p4 sync @committed changelist

Note

Your client's view mappings need to include the changelist's path.

Using P4V

For a shelved changelist:

  1. P4V "go to" menu option Select Search > Go To....

  2. P4V "go to" dialog with "Pending Changelist" selected Change the select box to Pending Changelist.

  3. P4V "go to" dialog with changelist entered Type in the shelved changelist number and click OK.

  4. P4V "Pending Changelist" dialog with shelved files selected Select the files in the Shelved Files area.

  5. P4V "Pending Changelist" dialog with content menu selecting "Unshelve..." Context-click, and select Unshelve....

  6. P4V "Unshelve" dialog Click Unshelve.

For a committed changelist:

  1. P4V "go to" menu option Select Search > Go To....

  2. P4V "go to" dialog with "Submitted Changelist" selected Change the select box to Submitted Changelist.

  3. P4V "go to" dialog with changelist entered Type in the submitted changelist number and click OK.

  4. P4V "Submitted Changelist" dialog with files selected Select the files in the Files area.

  5. P4V "Submitted Changelist" dialog with content menu selecting "Get this Revision"

    Context-click, and select Get this Revision.

  6. P4V dialog close button Click Close.

Using Git Fusion

A Review heading with Git logo Git Fusion-initiated reviews include the Git logo beside the main review identifier. This indicator is important because Perforce users cannot update Git Fusion-initiated reviews.

In the following example, the target branch is master, the review id is 773273, the Git Fusion hostname is gfserver, and the remote repo name is p4gf_repo.

  1. Fetch the review's head version:

    $ git fetch --prune origin
    From gfserver:p4gf_repo
     * [new_branch]      review/master/773273 -> origin/review/master/773273
     x [deleted]         (none)     -> origin/review/dev/new
    

    The --prune option lets the local Git repo delete the unwanted review/master/new reference created by the initial git push origin review/master/new command.

  2. Check out the review's head version:

    $ git checkout review/master/773273
    

Important

You can only update Git Fusion-initiated reviews using Git Fusion.

Tip

For more information on Git Fusion, see the Git Fusion Guide

0 matching pages