[Buildbot-devel] Diagnosing ignored changes?

[Dan Kegel]

I'm still using a fairly old master, v0.8.8-1082-g1554b09
I turned on gitlab webhooks recently, and they're mostly working fine.
Today, though, this change got ignored:

2015-05-19 09:52:09-0700 [HTTPChannel,248,10.10.169.27] Received 1
changes from gitlab
2015-05-19 09:52:09-0700 [HTTPChannel,248,10.10.169.27] Got the
following changes [{'files': [], 'project': '', 'repository':
u'git at gitlab.foo.com:astor/libastro.git', 'branch': u'rel-4.2',
'author': u'Brandon X(bbook) <brandon at foo.com>', 'when_timestamp':
datetime.datetime(2015, 5, 19, 9, 40, 28, tzinfo=tzoffset(None,
-25200)), 'revlink':
u'https://gitlab.foo.com/astor/libastro/commit/6c50b582ee712bd96111365faf625ee02c0f626b',
'comments': u'ob-style commit; only did this to make a commit \n',
'revision': u'6c50b582ee712bd96111365faf625ee02c0f626b'}]
2015-05-19 09:52:09-0700 [HTTPChannel,248,10.10.169.27] Payload: {}
2015-05-19 09:52:09-0700 [-] added change
Change(revision=u'6c50b582ee712bd96111365faf625ee02c0f626b',
who=u'Brandon X(bbook) <brandon at foo.com>', branch=u'rel-4.2',
comments=u'ob-style commit; only did this to make a commit\n',
when=1432053628, category=None, project=u'',
repository=u'git at gitlab.foo.com:astor/libastro.git', codebase=u'') to
database
2015-05-19 09:52:09-0700 [-] injected change
Change(revision=u'6c50b582ee712bd96111365faf625ee02c0f626b',
who=u'Brandon X(bbook) <brandon at foo.com>', branch=u'rel-4.2',
comments=u'ob-style commit; only did this to make a commit\n',
when=1432053628, category=None, project=u'',
repository=u'git at gitlab.foo.com:astor/libastro.git', codebase=u'')

Clicking 'force build' worked around it; the first log message that
generated was

2015-05-19 10:15:07-0700 [-] starting build <Build
libastro-osx109-rel-4.2-3.16> using slave <SlaveBuilder
builder='libastro-osx109-rel-4.2-3.16' slave='g-speak-xserve'>

What's the canonical way to diagnose why changes go into the ether
instead of triggering a build?

(As it turns out, the cause was probably that the builder was
configured with an https URL for that repo, but the webhook was
sending a git@ URL for the repo.
Switching the builder to use the git@ URL solved the problem.  I
wonder if we need a "Did you mean..." kind of warning when a change
doesn't match anything.)