OK so first off thanks for all the help getting things this far; we at
least are up and running with RB itself! Now to tie it all together.
Versions:
RBTools 0.6.2
VisualSVN server v2.5.7 Standard Edition on Windows 2008R2
ReviewBoard 2.0.5 on Centos 6.5
Submitters will be running AnkhSVN
You could either include credentials in your repository URL
(https://username:password@itt-d-cvs1.../.../), or try including the drive
name in the file:// URI (file://C:/data/SVNRoot/NetworkConfigs)
-David
On Thu, Aug 7, 2014 at 9:51 AM, Michael Kovacs dromin...@gmail.com wrote:
OK so first
Thanks David. None of the options worked... Here is three different configs
and the output of a snip of the post-commit.log file (names changed to
protect the innocent):
With parameters --repository-url=file:///c:/data/svnroot/NetworkConfigs
Making HTTP POST request to
What if you combine the first one (file://C:/...) with
--repository=Repository name?
-David
On Thu, Aug 7, 2014 at 12:19 PM, Michael Kovacs dromin...@gmail.com wrote:
Thanks David. None of the options worked... Here is three different
configs and the output of a snip of the post-commit.log
No joy there either. Tried with and without the repo name in the file://
call
Checking for a Subversion repository...
Running: svn info file://C:/data/SVNRoot/svn/ --non-interactive
Command exited with rc 1: ['svn', 'info',
'file://C:/data/SVNRoot/svn/', '--non-interactive']
svn: E180001:
Can you tell me what commands generated the output that you just sent?
-David
On Thu, Aug 7, 2014 at 1:10 PM, Michael Kovacs dromin...@gmail.com wrote:
No joy there either. Tried with and without the repo name in the file://
call
Checking for a Subversion repository...
Running: svn info
From a win8 desktop, I do a very simple edit of one text file:
svn co https://itt-d-cvs1.abc.local/svn/NetworkConfigs
cd NetworkConfigs
notepad test.txt (make small change in file)
svn ci -m 0807TestChgXX
The rest is done in the post-commit hook itemized above.
Just for clarity, this is the
Many thanks Christian.
If we're working in our own branch then what value should we use for
TRACKING_BRANCH
in .reviewboardrc?
At the moment we've committed .reviewboardrc, but perhaps we should add it
to git's ignore list and just set the TRACKING_BRANCH to our own working
area branch?
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3520 by matthias...@famsik.de: file shown in diff, altough no
changes on it
http://code.google.com/p/reviewboard/issues/detail?id=3520
*** READ THIS BEFORE POSTING!
***
*** You must complete this form in its entirety, or
