Post Review Error Uploading Diff Git
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company your review request still exists, but the diff is not attached. Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs the file was not found in the repository. (http 400, api error 207) Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, reviewboard the file was not found in the repository. just like you, helping each other. Join them; it only takes a minute: Sign up review board diff not uploading up vote 1 down vote favorite 3 i am currently attempting to do a diff using review
Reviewboard Upload Diff
board but keep getting an ambiguous error message: Error uploading diff Your review request still exists, but the diff is not attached. The debug messages do not give much away either, no errors whatsoever.... >>> RBTools 0.4.1 >>> Home = /home/tom >>> HTTP GETting api/ >>> HTTP GETting http://127.0.0.1/api/info/ >>> Using the new web API Index: /trunk/0.1/scripts/configure-apache.sh =================================================================== --- /trunk/0.1/scripts/configure-apache.sh (revision 143) +++ /trunk/0.1/scripts/configure-apache.sh (working copy) @@ -1,5 +1,5 @@ #! /bin/bash - +echo rbt post hello cd .. #SRCHEAD="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" SRCHEAD=$SRC_HEAD This is what my ".reviewboardrc" file contains: REVIEWBOARD_URL = "http://127.0.0.1/" the repository path is: "https://XXX/svn/infinity/trunk/0.1" does anyone know where i can start in order to resolve this issue i am seeing? thanks in advance apache svn unix code-review review-board share|improve this question edited Jul 5 '12 at 14:19 asked Jul 5 '12 at 13:29 godzilla 66442036 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote The problem you are facing may be that the relative path in the diff file is not correlated with the path of the repository as it is configured in Reviewboard. Reviewboard, in order to find in the repository the files mentioned in the diff, will concatenate the URLs like this: URL of the repo as configured in Reviewboard + optionally - the Base directory as it appears in the Reviewboard Upload diff dialog - which can be absolute/complete but also relative(!) + the relative path of the modified file as it appears in the diff file. All these must be correlated. Therefore, in your case, if your repository configured URL is: https://XXX/svn/infinity/trunk/0.1 and your relative path in the diff file is: /trunk/0.1/scripts/configure-apache.sh ... that will not work because the resulting absolute path of the file in
GoogleВойтиСкрытые поляПоиск групп или сообщений
Paths CVS and Subversion Distributed Version Control Systems ClearCase Posting Committed Code Posting Existing Diffs Automating post-review Configuration Repository Configuration Git Properties Perforce Counters Subversion Properties .reviewboardrc Internal post-review Configuration Custom User Configuration Options Basic Options Server Options https://www.reviewboard.org/docs/manual/1.5/users/tools/post-review/ Review Request Options Field Defaults Options ClearCase Options Git Options Git and Mercurial Options Perforce https://forums.open.collab.net/ds/viewMessage.do?dsMessageId=474119&dsForumId=736 Options Subversion Options Browse Prev: Tools Next: Administration Guide Table of Contents General Index You Are Here: Review Board Manual Users Guide Tools post-review post-review¶ Overview¶ post-review is a command line tool for Windows, Linux and MacOS X that simplifies both creating and updating review requests. It can look at your source directory, generate a diff, and upload the file it to a new or existing review request on an associated Review Board server. This saves a lot of time over the web UI, and for some types of code repositories (such as Perforce), it's actually required in order to produce a compatible diff. post-review is part of the RBTools package, and can be installed and upgraded by running: $ easy_install -U RBTools Posting and Updating Review Requests¶ Depending on the repository the file was type, post-review will either require a changeset number, or it will rely on the changes in the current source tree. The end result is that post-review will build a diff and post it to a Review Board server. The diff and any additional review request information will be saved on the server as a draft, which can then be published. After posting a new review request or updating an existing one, post-review will display the URL of the review request. If the -o parameter is passed, a browser will be opened to that URL. The following subsections will explain how post-review is used with different repository types. Perforce¶ Posting Changesets¶ Perforce has a concept of changesets, which are server-stored descriptions of a change along with an ID number and associated files. For Perforce, Review Board stores changeset numbers of a posted change and can use these to associate particular changes with review requests. To post a review request for a specific change, or to update an existing review request for that change, type: $ post-review CHANGENUM Where CHANGENUM is the changeset number in Perforce. The diff will be generated and uploaded to Review Board, and the review request information will be updated based on the changeset description. post-review must be used if you're using Perforce wit
and collaboration platform for enterprise agility TeamForge SCM Source code management platform for enterprise-grade Git and/or SVN CloudForge Hosted SVN ,Git and TeamForge projects Subversion Edge SVN Installation, updates & code management ScrumWorks Pro Agile Planning tool Integrations TeamForge plugins for your favorite tools Solutions By Need Hosted Services Enterprise SCM Agile Development By Industries Financial Services Government Healthcare Services Consulting Training Implementation Support Agile Training forums Error Error The discussion you referenced does not exist. This could occur if the discussion has been deleted or the URL has been edited. Please click on your browser's Back button, review your input, and try again. If you are still having problems please contact your administrator. Products TeamForge CloudForge ScrumWorks Pro Subversion Edge Enterprise Git GitEye Services Consulting Training Implementation Support Solutions Hosted Services Enterprise SCM Agile Development Financial Services Government Healthcare Resources White Papers Webinars Data Sheets Analyst Reports Case Studies Videos Company About Leadership Customers Partners Careers News & Events Locations Contact us Community Site Feedback Downloads TeamForge CloudForge ScrumWorks Pro Subversion Edge Enterprise Git GitEye Integrations Terms of Use Privacy Policy Copyright & Trademark Legal Copyright © 2015 CollabNet, Inc. All rights reserved. Global Sites Chinese Korean Japanese