tortoisesvn

I'm building a little prototype on my Windows machine. I've got Jenkins running, and am using TortoiseSVN as my repo, the location of which is at: file:///C:/SVNRepo When I try to add that as the repository URL in Jenkins I get the following error: Unable to access file:///C:/SVNRepo : svn: E180001: Unable to open an ra_local session to URL svn: E180001: Unable to open repository 'file:///C:/SVNRepo' Strangely enough that repository location works in Subclipse though. What am I missing to use TortoiseSVN with Jenkins? Ok, did some more digging and figured it out myself. I enabled command-line

Backstory : Got a job as an entry level web developer. Head developer leaves right when I start. All responsibility on me. Never used SVN. Going in blind. Problem : I keep getting errors like 'svn://svn/svn/xxx/project_name/branches/dev@330' must be ancestrally related to 'svn://svn/svn/xxx/project_name/trunk@326' The process by which I am starting the new project is: Make a directory for the project on my computer with subfolders: project_name/branches project_name/branches/dev project_name/tags project_name/trunk Right click the project root, select my project root, and Add it to the

I have experienced strange functionality of subversion. We are using latest 1.6 Svn server visual svn and tortoise svn 1.6.6 We have defined property svn:needs-lock to a file, then if you copy over file from different location it shows local change if you try to commit SVN it allows you to Commit even if you didn't obtain the LOCK. This is a big problem for us, please let us know how to force SVN not to allow commits without obtaining the lock. Thanks. The lock mechanism in Subversion will not give you, out of the box, a way to prevent commits without a lock first. You might, emphasis on might

After my previous problem, TortoiseSVN Can't Connect was resolved, I ran into a new problem. On the linux server hosting my svn repository, in the repository's directory, there is a conf/svnserve.conf file. In this file, I have the option: anon-access = none | read | write Initially, this line was commented out and the default value must have been read . Of course, I want to set anon-access = none , and I want auth-access = write (which is the default). But when I set anon-access = none , when I try to browse with TortoiseSVN Repository Browser using url svn://host:port/repositoryname , I get

I am trying to delete a folder within my Subversion repository. My TortoiseSVN client gives me the following error message when I try to commit this change: Commit Failed (details follow): User {username} does not own lock on {path} page {filename} currently locked by {another user} If you want to break the lock, use the 'Check for modifications' dialog. I do want to break the lock and delete the folder, but I can't see an obvious way to do it from the Check for Modifications folder. Does anyone have any suggestions? dthrasher From Pedro's answer, I was able to figure out how to do this from

I was going to ask this in tigris.org, however they have maintenance in their forum. My environment: Windows 7 x64, Tortoisesvn latest x64, simple repo. What I'm doing: I am adding a new file to repo, then doing SVN Commit. This operation is successful and I can see it in repo from trac or directly. I expect: To see that file's icon as green checkmark. What I have: I see blue PLUS icon, like I haven't done commit. However, if I just create any new file in that folder(without any commit or update), the icon is immediately changing to checkmark. What a magic! I don't expect here anyone to have

I have Jira and Fisheye setup so that I can include Jira key in the commit comment ( Smart Commits ). Fisheye will link source code and Jira issue mentioned in the commit. I would not like to use something like JIRA Commit Acceptance Plugin to decline commits without Jira keys. As it is too restrictive. But would still like to monitor commits without Jira keys. How to get a report of all SVN commits that do not include Jira bug Key in the comment? You can run following command on UNIX in the directory with your working copy: svn log | grep -v '\--' | awk 'ORS=(NR%3)?" ":"\n"' | grep -v "[ISSUE