Improve server debugging experience

[mpacer]

Right now it's not straight-forward to debug the server, because the easiest way to actually deposit a payload to a running server is to actually create a new PR that meets the Paper: naming criteria on scipy-conference/scipy_proceedings.

There are a number of things to improve:

• trigger individual builds
• trigger the webhook

[stefanv]

The first should be much easier, once we complete the message bus work.

The second we can do by making a POST to the webhook URL with the following format data:

{
  'pull_request': {
    'html_url': 'https://github.com/scipy-conference/scipy_proceedings/pull/335'
  }
}

We can write a script with a signature like trigger_webhook.py N where N is a paper number, then look up the PR url in the cache, and do the POST request as outlined above.

[mpacer]

I think we’ll need more header information when tying to debug this in the past.

[mpacer]

Also, I’m not sure how we’re going to redirect the Webhook calls from
GitHub to the appropriate location at procbuild.scipy.org

[stefanv]

The README explains how to add a webhook:

In the scipy-conference/scipy_proceedings repo: in the webhooks add a payload
URL pointing to the webapp (such as http://server.com:5000/webhook). You must
select only Pull Requests in the checkbox menu.

[stefanv]

I think we’ll need more header information when tying to debug this in the past.

Can you explain what you mean by this?

[mpacer]

Sorry, my tenses got messed up.

When I was trying to mock up these requests with Katy last year we needed more header information from the GitHub webhook for the request to work properly. I don’t remember what that information was off the top of my head.

[stefanv]

You can see the code that handles the incoming request here: https://github.com/scipy-conference/procbuild/blob/master/procbuild/server.py#L249

It only reads the fields I mentioned.