From afe029ca9a29fc73935ae3441aaad9e68f6ed34b Mon Sep 17 00:00:00 2001
From: Teddy Wing
Date: Fri, 10 Nov 2017 02:10:49 +0100
Subject: main(): Make endpoint to handle GitHub webhook

Convert our dummy test route to a real one that will handle webhooks
coming from GitHub. It will parse the POST body data and create a
`CommitRef` from it. That `CommitRef` then gets passed to
`find_and_track_build_and_update_status()` to update the pull request
status based on Jenkins' build results.

A 202 response seemed apt here. Quoting
https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html:

> 10.2.3 202 Accepted
>
> The request has been accepted for processing, but the processing has
> not been completed. The request might or might not eventually be acted
> upon, as it might be disallowed when processing actually takes place.
> There is no facility for re-sending a status code from an asynchronous
> operation such as this.
---
 src/lib.rs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'src/lib.rs')

diff --git a/src/lib.rs b/src/lib.rs
index add79dd..a4cfffb 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -1,4 +1,5 @@
-mod pull_request;
+pub mod jenkins;
+pub mod pull_request;
+
 mod github;
-mod jenkins;
 mod af83;
-- 
cgit v1.2.3