Oh ok, thanks for the info! We typically just use the IDE to generate a
.patch file and then upload it to reviewboard. The projects in our IDE are
usually set up as one for trunk and one for each branch, so when it
generates the .patch files it generates them with relative paths using
/trunk or /branches/<branchversion> as the "root" directory, so that's why
we have the repositories configured that way in ReviewBoard. If we change
the repo configuration in ReviewBoard around to not target the individual
branches then we'd have to start hand editing the patch files after
generating them to make sure the path in there references the full path
including the branch. It looks like this woud be the case even if using
RBTools because I don't see a way for RBTools to target a changelist, or am
I missing something? We might have 4 or more separate changelists at any
given time in the IDE and those could encompass hundreds of files, so
targeting a whole changelist for posting the review is pretty crucial for
us. Is there a way for RBTools to do this?
On Thursday, May 28, 2015 at 6:32:06 PM UTC-4, Christian Hammond wrote:
> If svn/Repo1, svn/Repo2, etc. are all independent Subversion repositories,
> and not subdirectories within a larger repository, then you should have a
> repository entry in Review Board for each.
> You shouldn't target trunk, branches, etc., because those are
> subdirectories. When posting a change for review against a Subversion
> repository, RBTools will send paths that are relative to the root of the
> repository (say, /trunk/myproject/README). That then gets accessed relative
> to the repository path, giving you something like
> https://vcs.ourdomain.com/svn/Repo1/trunk/myproject/README, or, if
> misconfigured, something like
> To fix things up by hand, you'll need to modify the diffviewer_filediff
> table entries (or FileDiff in the database editor in the admin UI) and
> change the paths shown there. The trick is associating the entries with a
> given review request. For that, you can try something like:
> $ rb-site manage /path/to/site shell
> >>> from reviewboard.diffviewer.models import FileDiff
> >>> print
> FileDiff.objects.filter(diffset__history__review_request=<review request
> ID>).values_list('pk', 'source_file')
> Where "<review request ID>" is replaced with the numeric ID of the review
> reuqest. That would show you all FileDiff IDs and their paths for a given
> review request.
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
> -----Original Message-----
> Date: May 28, 2015 at 2:32:20 PM
> Subject: Re: After upgrading to ReviewBoard 2.0.15 the existing reviews
> do not display the diffs correctly
> > Ok, thank you.
> > If I wanted to go through and fix the paths of the existing reviews,
> > tables, specifically, would I need to go through and look at?
> > Aslo, this may be a dumb question, but I'm not the most Subversion savvy
> > person in the world. We have our repositories set up like
> > https://vcs.ourdomain.com/svn/
> > and then we have the Repositories within there, like
> > https://vcs.ourdomain.com/svn/Repo1
> > https://vcs.ourdomain.com/svn/Repo2
> > and then each repository has
> > https://vcs.ourdomain.com/svn/Repo1/trunk
> > https://vcs.ourdomain.com/svn/Repo1/branches
> > https://vcs.ourdomain.com/svn/Repo1/branches/2012.REL
> > https://vcs.ourdomain.com/svn/Repo1/branches/2013.REL
> > ...
> > Are you saying we'd need to point straight to
> > https://vcs.ourdomain.com/svn/Repo1/ in order for Reviewboard to work
> > correctly, or can we target trunk or individual branches, etc.?
> > On Wednesday, May 27, 2015 at 12:28:40 PM UTC-4, Papaswede wrote:
> >> I upgraded ReviewBoard from 1.6.11 to 2.0.15. After doing this, I get
> >> error messages when attempting to view the diffs of the existing
> reviews. I
> >> get messages like:
> >> The file
> >> path not found", 160013)' could not be found in the repository
> >> Where that path definitely is not a valid svn path. It should
> >> be
> >> So, it's like there's stuff being automatically inserted into the svn
> >> for the file, but I have no idea why as it was working on version
> >> Any help would be greatly appreciated.
> > --
> > Supercharge your Review Board with Power Pack:
> > Want us to host Review Board for you? Check out RBCommons:
> > Happy user? Let us know! https://www.reviewboard.org/users/
> > ---
> > You received this message because you are subscribed to the Google
> Groups "reviewboard"
> > group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > For more options, visit https://groups.google.com/d/optout.
Supercharge your Review Board with Power Pack:
Want us to host Review Board for you? Check out RBCommons:
Happy user? Let us know! https://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.