tag:help.lighthouseapp.com,2008-09-20:/discussions/api-developers/13-svn-integrationLighthouse: Discussion 2011-04-07T05:34:24Ztag:help.lighthouseapp.com,2008-09-20:Comment/106882007-08-28T05:44:31Z2009-06-20T20:55:58ZSVN Integration<div><p>Where the heck is the variable "url" coming from on line 53 and
line 58?</p>
<p>I'm assuming you mean uri. But still stuff was broken. I hacked
it up so it eventually works. Heres what I used:
http://pastie.caboo.se/91625</p>
<p>Also, the options arent self explanatory at all (at least not
for me without debugging for a couple hours).</p>
<p>TIP: Replace :project => "" to the ID of your project (found
in the query string)</p>
<p>Replace :account => "" to the url of your lighthouse app
"http://[project_name].lighthouseapp.com"</p>
<p>Its very easy to leave "activereload.lighthouseapp.com" in there
and all you get is a bunch of friggin 401 authorized denied
errors.</p></div>jacquestag:help.lighthouseapp.com,2008-09-20:Comment/106882008-03-30T14:18:03Z2009-06-20T20:56:14ZSVN Integration<div><p>I've did my best but unfortunately i'm unable to synchronize git
and svn repositories. I believe i've done everything according to
the 'help' but i'm stumbling upon 'Error: 401 Unauthorized' again
and again. All the data (token, account ID, project ID) i'm
providing is proper for 100%. Is there anything else you have to
setup in the system to make it work? Setup a milestone? task?</p>
<p>Any help will be greatly appriciated</p>
<p>Best regards Michal</p></div>eclectictag:help.lighthouseapp.com,2008-09-20:Comment/106882008-03-30T17:39:47Z2009-06-20T20:56:14ZSVN Integration<div><p>You need a correct token too. The token basically authorizes you
for the given account/project.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/106882008-03-30T19:34:59Z2009-06-20T20:56:14ZSVN Integration<div><p>Obviously i create a token, testet with one to one project and
one to all projects.</p></div>eclectictag:help.lighthouseapp.com,2008-09-20:Comment/106882008-09-24T01:25:53Z2009-06-20T20:01:32ZSVN Integration<div><p>We have a repo with many projects, so the whole idea of having
this not handle multiple projects just wasn't working. I modified
the example script to now handle multiple projects. It will check
all of the changed files in the script against a regex that is
supplied for each lighthouse "project ID". If it finds a match, it
will assume the changeset applies to that project. It will check
all file changes against all project regexes, so a changeset might
actually match two projects. In that case, it will submit one
changeset under each of the affected Lighthouse projects.</p>
<p>Here's what the project option looks like now--a hash of project
IDs to regular expressions, a positive match of which indicates
that the changeset applies to that project ID:</p>
<p>:project => { 1234 => /\/projectA\//i, 1235 =>
/\/projectB\//i },</p>
<p>Here's the code--enjoy!</p>
<p>http://pastie.org/278206</p>
<p>-Matt Lightner</p></div>Matt Lightner