Redmine

Hi dah woo,

(1) this can be seen after you have created a svn repository on your svn server and told redmine where to find it.
The basic integration simply alows to browse the repository and to react to commits.
This is done by redmine regularly looking at the commit messages on the server.

(2) You will have to create the repository on your svn server.
If it is the same machine that runs redmine, you would simply create a new repository using svnadmin create.

So the single steps to get your basic svn integration running are:

1. decide where/how to serve subversion
2. create the repo on the svn server
3. tell redmine about it in project => settings => repositories => create

You might want to consider to use a preconfigured stack like bitnami that already comes with a subversion server on the same box.
Alternatively, there are open source svn servers like CollabNet's Subversion Edge and VisualSVN Server that would make it easier to manage your svn repositories.

Best
Volker

Hi Volker, thanks for your reply. I thought about chasing down file structure from a stack but that inevitably means I'll have to spend another few days setting one up and really going through the settings to make sure my settings are correct. Ultimately (for reasons unknown) we don't want to use the stack. Thanks for helping me along

Also thanks again for your tips on the repository creation. I did create a couple of repositories but I am not seeing them in redmine so my new questions are:
1) if I created the repository in redmine first (before doing it via SVN) does that make a difference? should I still be able to see it? I used the same identifier when I created in commandline
2) also I am not able to connect to it svn from an outside machine. I tried using windows and it said I was not authenticated to get to it. permissions maybe?

also... I just checked permission on /svn and opt/repositories/svn and they are both set to root/root (owner/group). I'm guessing this is incorrect. I have two folders because I tried two different methods of getting this to work and have been in circles the last few days trying everything I could think of or find. I will ultimately remove the one that does not work.

additionally, say my opt/repositories/svn file path is the correct one.. should I be changing ownership on /opt recursively?

Still looking to resolve this. I didn't have any time to look into this since I last posted but would like a little further assistance if anyone happens to be available. Thanks

Hi dah woo,

• is red mine and SVN running on one machine/server?
• Are the two systems on different machines?
• Can you SVN from a client software as tortoiseSVN?

• Did you install SVN with the appropriate apache SVN module?
• Or: How do you else want to access it? SVN protocol, SVN+SSH?
• Did you install/setup the Credential handling for Redmine?
  

  http://www.redmine.org/projects/redmine/wiki/HowTo_configure_Redmine_for_advanced_Subversion_integration
  

• Depending on you SVN config, it becomes necessary to allow any client to access the SVN repos one-by-one in the config. Do not forget to allow Redmine serving server itself to access it.
• My experience is that SVN should run in /var/www and with apache (www-data) access rights in user and group. This also is mandatory for the svn repos itself
• As Volker mentioned, the very access via Redmine is only reading and showing the last commits on the main repo.

Also, as Volker mentioned, have a Bitnami stack "Redmine" installed as reference. It could help ya figure out.
Can you re-summarize the issues you have in detail?

BR

Hi Buzze! Thank you so much for your detailed email. I have commented below inline in bold writing. I had to take a break from this and get some work done in the field. Hopefully my replies make sense. I plan to attack this again over the next couple of days. Thanks so much again for jarring info out of me to help get my issue resolved.

Buzze Kr ies wrote:

Hi dah woo,

I can't quite figure out from ya post:

• is red mine and SVN running on one machine/server? yes they are running on the same server but I set it up (or I used the setup to use the http:// instead of file:/// so that i could move it later if I wanted to to)
• Are the two systems on different machines? No. Same machine
• Can you SVN from a client software as tortoiseSVN? I tried using tortoise but I could not login. I think my permissions may be wrong?!?

My suggestions/questions:

• Did you install SVN with the appropriate apache SVN module? I thought I did but I am not seeing it. I have to dig deeper and get that answer back to you
• Or: How do you else want to access it? SVN protocol, SVN+SSH? I would like to access it any way possible at this point so that I know it's working. Then I will work on the advanced/automated portion. Currently I can create a project via SSH and I see it in the file structure so I know that part worked however I can not access it from tortoise when I try to import
• Did you install/setup the Credential handling for Redmine? I did
  [...]
• Depending on you SVN config, it becomes necessary to allow any client to access the SVN repos one-by-one in the config. Do not forget to allow Redmine serving server itself to access it.
• My experience is that SVN should run in /var/www and with apache (www-data) access rights in user and group. This also is mandatory for the svn repos itself redmine is running in var/www/ but I am on centOS 6 not using debian/ubuntu so "www-data" is just "apache" but I'm not sure if I should give permissions to apache on the SVN folder? yes or no?
• As Volker mentioned, the very access via Redmine is only reading and showing the last commits on the main repo. I understand this

Also, as Volker mentioned, have a Bitnami stack "Redmine" installed as reference. It could help ya figure out. I was debating on doing that but it's more time and having to set up on another machine and I feel like i am really close to solving the problem here. Worst case scenario is i will do that and rip through the files and sort it out.
Can you re-summarize the issues you have in detail?

BR

Also here are the permissions for my SVN directory. Is "root" correct? or should be be "apache" (www-data for those using ubuntu)??

[root@s18409075 ~]# ls -l /opt/repositories/svn
total 4
drwxr-xr-x 6 root root 4096 Jul 12 09:27 test

***Test is the first repository I created via command line. It is also the one I can not get to using tortoise. I suspect that is yet another permissions error.

Another update... I ran the reposman file and it kicked back an error saying the file couldn't be found. ran again using the /path/to/reposman and it kicked back a message saying I needed to install two more gems. I did that and ran reposman again. Voila! it worked. I then used tortoise and after a few tries was able to checkout a repository. So i am almost there. So as far as I can tell the only two things I have left are editing the crontab and getting redmine to see the repositories that were created for each project.

I'd like to get the redmine portion working first. when I go to the project >> Settings >> repositories I can see the repository was created and that redmine is aware that it exists however when I'm simply in the project itself and click on the repositories tab I get a 404 error saying it doesn't see it. I'll continue to dig into this but if someone knows why that might be. please do let me know.

Thanks!

Good work.
As far as I understood your last task is to solute the 404 when accessing the repo in Redmine?
Correct?
Please consult your apache2 error log.

If I were you, I'd chmod the SVN files (recursively (-R)) to apache:apache. (According to Debian www-data)
But I came over the fact, that it is depending on how the machine with SVN was set up.

BR

Buzze Kr ies wrote:

Good work.
As far as I understood your last task is to solute the 404 when accessing the repo in Redmine?
Correct?
Please consult your apache2 error log.

If I were you, I'd chmod the SVN files (recursively (-R)) to apache:apache. (According to Debian www-data)
But I came over the fact, that it is depending on how the machine with SVN was set up.

BR

my apache error log doesn't appear to be much help. I don't see any errors in there since I've solved my problem today. i can post the results. if needed.

I will try the apache:apache permissions update in the morning. Looking back at your previous post I'm not 100% sure I can verify but since it is partially working I had to have at least done most of what you are mentioning.

had a small setback but I was able to recover. I was trying so many solutions that I couldn't remember them all and I lost some control. In any event I'm back to where I was previously with being able to login via the browser directly to svn repo. "http://my.site/svn/repo" I get login credentials and i can browse files for projects ONLY if I have files in the projects repo. If there are no files I get an authentication error. Will check log after I post this.

From Tortoise I can connect to all repos using various users that I have setup in redmine regardless if I have files or not. (this is how I got files into two of the repo's)

I still can not see any repos from the redmine interface repositories tab. I found this link http://www.inflightmagazine.co/category/sys-admin/ which I thought would help but did not for a couple of reasons. 1) I'm not using HTTPS and 2) I couldn't login as su apache. I kept getting the message "This account is currently not available" if I bash and force apache I login but I never get asked certificate questions. This is what I get when I bash:

ATTENTION!  Your password for authentication realm:

   <http://my_site.com:80> Subversion Repository

can only be stored to disk unencrypted!  You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible.  See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/var/www/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)? yes 

I'm puzzled to say the least.

Error log tidbits:

redmine_error_log: (/var/log/httpd)
try to go to http://mysite/svn/project_ID that has no files and I get this:

access to /svn/projectID/ failed, reason: verification of user id 'user_name' not configured

If the project has files I get no new errors.

production.log (/var/www/redmine/log/) (I used tail command to grab the last 100 lines only. I did not sift through the entire log)

<list
   path="http://wwww.my_site.com/svn/project_ID">

  Rendered common/error.html.erb within layouts/base (0.2ms)
Completed 404 Not Found in 275ms (Views: 27.1ms | ActiveRecord: 3.3ms)
[root@s18409075 log]# tail -n 100 production.log
/var/www/redmine/lib/redmine/scm/adapters/subversion_adapter.rb:97:in `block in entries'
/var/www/redmine/lib/redmine/scm/adapters/abstract_adapter.rb:254:in `call'
/var/www/redmine/lib/redmine/scm/adapters/abstract_adapter.rb:254:in `block in shellout'
/var/www/redmine/lib/redmine/scm/adapters/abstract_adapter.rb:251:in `popen'
/var/www/redmine/lib/redmine/scm/adapters/abstract_adapter.rb:251:in `shellout'
/var/www/redmine/lib/redmine/scm/adapters/abstract_adapter.rb:208:in `shellout'
/var/www/redmine/lib/redmine/scm/adapters/subversion_adapter.rb:94:in `entries'
/var/www/redmine/app/models/repository.rb:200:in `scm_entries'
/var/www/redmine/app/models/repository.rb:205:in `entries'
/var/www/redmine/app/controllers/repositories_controller.rb:116:in `show'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/abstract_controller/base.rb:198:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:92:in `_run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:776:in `_run_process_action_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `block in instrument'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `instrument'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.2.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/abstract_controller/base.rb:137:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionview-4.2.1/lib/action_view/rendering.rb:30:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal.rb:196:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_controller/metal.rb:237:in `block in action'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:74:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/journey/router.rb:30:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/journey/router.rb:30:in `serve'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:819:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-openid-1.4.2/lib/rack/openid.rb:98:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/request_store-1.0.5/lib/request_store/middleware.rb:9:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/etag.rb:24:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/conditionalget.rb:25:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/head.rb:13:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-xml_parser-1.0.2/lib/action_dispatch/xml_params_parser.rb:16:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/flash.rb:260:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/session/abstract/id.rb:225:in `context'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/session/abstract/id.rb:220:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.2.1/lib/active_record/query_cache.rb:36:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:649:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:88:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:88:in `_run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:776:in `_run_call_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/rack/logger.rb:38:in `call_app'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/rack/logger.rb:20:in `block in call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:68:in `block in tagged'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:26:in `tagged'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:68:in `tagged'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/rack/logger.rb:20:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/methodoverride.rb:22:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/runtime.rb:18:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.2.1/lib/action_dispatch/middleware/static.rb:113:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.6.1/lib/rack/sendfile.rb:113:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/engine.rb:518:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/application.rb:164:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/railtie.rb:194:in `public_send'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.2.1/lib/rails/railtie.rb:194:in `method_missing'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.9/lib/phusion_passenger/rack/thread_handler_extension.rb:94:in `process_request'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.9/lib/phusion_passenger/request_handler/thread_handler.rb:149:in `accept_and_process_next_request'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.9/lib/phusion_passenger/request_handler/thread_handler.rb:110:in `main_loop'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.9/lib/phusion_passenger/request_handler.rb:414:in `block (3 levels) in start_threads'
/usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.9/lib/phusion_passenger/utils.rb:111:in `block in create_thread_and_abort_on_exception'
...
No close tag for /lists/list
Line: 4
Position: 89
Last 80 unconsumed characters:

Output was:
 <?xml version="1.0"?>
<lists>
<list
   path="http://wwww.my_site.com/svn/project_ID">

  Rendered common/error.html.erb within layouts/base (0.2ms)
Completed 404 Not Found in 275ms (Views: 27.1ms | ActiveRecord: 3.3ms)

This is the only error I see in the production.log when I select the repository tab of a project

Error parsing svn output: #<REXML::ParseException: No close tag for /lists/list>

Any ideas anyone? I'm pretty stumped. Also, my reposman crontab creation appears to be running (I have used $ tail /var/log/reposman.log & tail /etc/cron.d) but the repository is not being created. If I manually run the command the repositories get created right away. What could be my issue there?

Sorry to say: But I am out. No more ideas here.

What I would do: Set up a virtual machine and re-setup CentOS + Redmine + SVN.
Save a Snapshot or export VM after any major step succeeded.
Step back when necessary.
When everything works fine: Move to a live environment.

Sorry.
BR
B.

OK... I spent some time on this today and am able to get both sides working. I've ditched the URL for external IP and I am using the local file structure commands (ie file:///path/to/repos/svn/projectID) I am stuck at the final stage... I have the cron setup and I can see it running when I watch the cron log (Currently set to run every 2 minutes while I am testing). Someone can surely help me get this sorted out. The issue I have is that the crontab is not creating the repo's for new projects. If I run the reposman.rb file as root user it does create them. Please help.

Here is what I have I have in my cron located in /etc/cron.d/redmine

*/2 * * * * root ruby /var/www/redmine/extra/svn/reposman.rb --redmine localhost --svn-dir /opt/repositories/svn --owner apache --url file:///opt/repositories/svn/ --key=MY_API_KEY >> /var/log/reposman.log

as I said before I can see it running. I have also tried it as apache in the crontab and it didn't work

Any help will be greatly appreciated. Let me know if you need more info from me.