From df9b4dbd7aa8401b0e488c99c49205bc39dc5a80 Mon Sep 17 00:00:00 2001 From: Teddy Wing Date: Mon, 13 Nov 2017 23:07:28 +0100 Subject: Focus HTTP response logging on `update_commit_status()` Comment out HTTP response logging from Jenkins because those may be coming back all right. Actually I might want to leave the log from `request_job()` now that I think about it. Add some additional logging on `update_commit_status()` to hopefully try to see why it's not getting called all the time. --- src/github.rs | 3 +++ src/jenkins.rs | 4 ++-- 2 files changed, 5 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/github.rs b/src/github.rs index 9b95192..44a4419 100644 --- a/src/github.rs +++ b/src/github.rs @@ -93,6 +93,9 @@ pub fn update_commit_status( .json(¶ms) .send()?; + debug!("{}", response.url()); + debug!("{}", response.status()); + debug!("{}", response.headers()); debug!("{}", response.text()?); Ok(()) diff --git a/src/jenkins.rs b/src/jenkins.rs index c954846..61d3bf1 100644 --- a/src/jenkins.rs +++ b/src/jenkins.rs @@ -231,7 +231,7 @@ pub fn get_jobs( let body = response.text()?; - debug!("{}", body); + // debug!("{}", body); let jobs = json::parse(body.as_ref())?; @@ -257,7 +257,7 @@ pub fn request_job( let body = response.text()?; - debug!("{}", body); + // debug!("{}", body); let job = Job::new(body)?; -- cgit v1.2.3