SVN Integration

Rick's Avatar


25 Aug, 2007 06:19 AM

Some folks have been having issues dealing with the escaping of single quotes in changesets that they're posting. I tried a few things and got some weird results back. James Cox was nice enough to remind me that the Net/HTTP library works just fine and should be available for anyone that has a proper ruby installation.

So, check out the new and improved SVN integration script.

  1. 1 Posted by jacques on 28 Aug, 2007 05:44 AM

    jacques's Avatar

    Where the heck is the variable "url" coming from on line 53 and line 58?

    I'm assuming you mean uri. But still stuff was broken. I hacked it up so it eventually works. Heres what I used:

    Also, the options arent self explanatory at all (at least not for me without debugging for a couple hours).

    TIP: Replace :project => "" to the ID of your project (found in the query string)

    Replace :account => "" to the url of your lighthouse app "http://[project_name]"

    Its very easy to leave "" in there and all you get is a bunch of friggin 401 authorized denied errors.

  2. 2 Posted by eclectic on 30 Mar, 2008 02:18 PM

    eclectic's Avatar

    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?

    Any help will be greatly appriciated

    Best regards Michal

  3. 3 Posted by Rick on 30 Mar, 2008 05:39 PM

    Rick's Avatar

    You need a correct token too. The token basically authorizes you for the given account/project.

  4. 4 Posted by eclectic on 30 Mar, 2008 07:34 PM

    eclectic's Avatar

    Obviously i create a token, testet with one to one project and one to all projects.

  5. 5 Posted by Matt Lightner on 24 Sep, 2008 01:25 AM

    Matt Lightner's Avatar

    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.

    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:

    :project => { 1234 => /\/projectA\//i, 1235 => /\/projectB\//i },

    Here's the code--enjoy!

    -Matt Lightner

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac