Changes between Version 29 and Version 30 of CodeReviewerPlugin

Timestamp:

Dec 24, 2016, 3:40:56 AM (7 years ago)

Author:

Ryan J Ollos

Comment:

Update for new trac-admin codereviewer resync command.

CodeReviewerPlugin

@@ -46 +46 @@
  1. Install the plugin, after downloading and unzipping:
  {{{#!sh
-cd codereviewerplugin/0.12
-sudo python setup.py bdist_egg
-sudo cp dist/TracCodeReviewer*.egg /your/trac/location/plugins/
+$ cd codereviewerplugin/0.12
+$ sudo python setup.py bdist_egg
+$ sudo cp dist/TracCodeReviewer*.egg /your/trac/location/plugins/
 }}}
 
@@ -71 +71 @@
  4. After the above, upgrade your Trac environment:
  {{{#!sh
-sudo trac-admin /path/to/projenv upgrade
+$ sudo trac-admin /path/to/projenv upgrade
+}}}
+
+ 5. Resync the repository
+ {{{#!sh
+$ sudo trac-admin /path/to/projenv codreviewer resync <repos>
 }}}
 
@@ -114 +119 @@
 In the example above, each time a code review is submitted for a completed ticket, the {{{stage_deploy}}} Jenkins job gets triggered. The job would then call [browser:codereviewerplugin/0.12/coderev/util/reviewer.py Reviewer.get_next_changeset()] to determine what git changeset to deploy (if any). Note that this trigger for, say, a stage environment would be in addition to any trigger for running tests against the HEAD of your branch, or however you may currently have your CI system set up.
 
-==== Ticket-changeset map
-
-In order for the [browser:codereviewerplugin/0.12/coderev/util/reviewer.py Reviewer] to know all changesets that reference a given ticket, it needs a reliable ticket-changeset map. The built-in {{{revision}}} table is unfortunately not sufficiently reliable for some version control systems, eg Git. This is a known issue. So this plugin comes with its own changeset listener that manages a new {{{codereviewer_map}}} table. For existing changesets, you can run a provided [browser:codereviewerplugin/0.12/coderev/util/sync.py sync.py] utility once to populate the table, but should not need it after that.
-
 ==== Completeness criteria