tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/655-changesets-from-beanstalk-not-appearingLighthouse: Discussion 2011-04-07T05:35:20Ztag:help.lighthouseapp.com,2008-09-20:Comment/1229282009-04-05T22:02:28Z2009-04-05T22:02:28ZChangesets from Beanstalk not appearing<div><p>I double checked my account settings and I'm not seeing anything
out of place; I haven't changed (to my knowledge) either my
Beanstalk account (still set up for Lighthouse integration) nor my
Lighthouse token configurations. Yet, I don't see any recent
commits in my Lighthouse dashboard since March 13. Should be some
from last week as well as today.</p>
<p>Thoughts? What should I look at first?</p>
<p>Side note: I recently started trying to update tickets with
commit statements; I realized a few commits in that the Lighthouse
help page has "[\#X]" (backslash included) and I was doing that
verbatim in my commits in Versions.app until I read the LH
integration guide on Beanstalkapp.com that omitted the backslash.
Is it possible that those commits with backslashes have errored out
and caused all my commits to queue up for processing / integration
with LH? A stretch, I know.</p>
<p>(Update: the backslash isn't appearing in this report, but note
the backslashes on
http://help.lighthouseapp.com/faqs/ticket-workflow/ticket-keyword-updates
- maybe these are required because the examples are command
line?)</p></div>Scott Heaberlintag:help.lighthouseapp.com,2008-09-20:Comment/1229282009-04-06T04:04:59Z2009-04-06T04:04:59ZChangesets from Beanstalk not appearing<div><p>Jobs definitely aren't queuing up. The backslash isn't required
at all, it's so the custom text formatter doesnt convert #NUMBER
into a link to a ticket: <a href="/discussions/problems/123" title=
"Discussion #123">#123</a>. I suppose I'll have to fix the
formatter so #NUM shows up as just #NUM.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1229282009-04-07T02:27:50Z2009-04-07T02:27:50ZChangesets from Beanstalk not appearing<div><p>Well, changesets are showing up; I guess I was just being silly.
I coulda sworn some were missing, but now that I see some from this
weekend, I'm marking this resolved. Sorry for crying wolf.</p></div>Scott Heaberlintag:help.lighthouseapp.com,2008-09-20:Comment/1229282009-04-07T02:29:54Z2009-04-07T02:29:54ZChangesets from Beanstalk not appearing<div><p>Ha. Well that's cool that they are there now. If you notice it
again, please let us know.</p></div>Will Duncan