github integration

Gennady Borukhovich's Avatar

Gennady Borukhovich

17 Apr, 2009 11:20 AM

I setup github/lighthouse integration by generating the key, inputting it into the github service hooks, etc. I also tested the integration from github by clicking "test hook" and when i manually tested it that way, i saw my last 2 or so changesets in lighthouse. However, I have not seen any changesets come into lighthouse automatically. What am i doing wrong?


  1. 1 Posted by Will Duncan on 17 Apr, 2009 11:28 AM

    Will Duncan's Avatar

    In your github account, can you check to make sure the hook is set to active? there is a check mark next to where you enter your Lighthouse key.

  2. 2 Posted by Gennady Borukho... on 17 Apr, 2009 11:45 AM

    Gennady Borukhovich's Avatar

    Somehow, this is working this morning, i'm not sure what was up prior to this morning. But to answer your question, i had it active the whole time.


  3. 3 Posted by Will Duncan on 17 Apr, 2009 11:47 AM

    Will Duncan's Avatar

    That's really strange, but I'm glad it's working. If it happens again, please let us know...

  4. 4 Posted by rey.write on 18 Apr, 2009 02:24 AM

    rey.write's Avatar

    It takes a while for changesets to register in Lighthouse, it is not automatic, even if they are shown in Github at the time.

  5. 5 Posted by michal.szajbe on 18 Apr, 2009 11:55 AM

    michal.szajbe's Avatar

    Yes, there is a tiny delay between commits are pushed to GitHub and tickets are updated on LightHouse.

    However there seem also to be a delay between marking ticket as resolved (by GitHub commit) and ticket disappearing from ticket list of current milestone.

  6. 6 Posted by Rick on 19 Apr, 2009 06:41 PM

    Rick's Avatar

    Changesets showing in the Lighthouse timeline really depend on when Github sends them. The ticket updates are thrown into our job queue and can take little longer (usually much less than a minute). What kinds of delays are you seeing?

  7. 7 Posted by rey.write on 19 Apr, 2009 06:50 PM

    rey.write's Avatar

    It usually takes anywhere from 30 secs to 1 minute for them to register, which is to be expected, since the change actually has to be pushed to github, registered on github, and then sent to lighthouse and show up there (at least I'm guessing that's how the workflow/api works). It's somewhat expected.

  8. 8 Posted by michal.szajbe on 19 Apr, 2009 11:44 PM

    michal.szajbe's Avatar

    I am aware that delays between github and lighthouse are normal thing.
    However I am talking about following situation:

    I commit a change to github, ticket gets resolved at Lighthouse (I see
    it's resolved on ticket's page: projects/X/tickets/Y). I go to current milestone's tickets (projects/X/milestones/current)
    and I see that ticket there still marked as new. Seems like no
    automatic cache expiration after ticket update by github. The ticket disappears from current milestone's tickets list only after
    I manually update another ticket. Like this action actually expires

    Hope that's more clear now :)

  9. 9 Posted by Rick on 20 Apr, 2009 04:49 PM

    Rick's Avatar

    Thanks michal, that's clearly an expiration bug. I'll get that fixed today.

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