search

rsm-hcd / hubot-jenkins-enhanced

Jenkins integration for Hubot with multiple server support
MIT License
31 stars 33 forks source link

HTTP 400 - Bad request. #12

Open mchennamsetty opened 7 years ago

mchennamsetty commented 7 years ago

First of all, thanks for your contribution towards this project. I have tried make it work. But having a weird issue. Its throwing Error 400. I have tested it using Postman successfully using the URL (http://dhud001:6900/apprel/api/json) and basic auth. Any idea what might be causing this issue.

[Thu Jun 01 2017 08:21:17 GMT-0500 (Central Daylight Time)] DEBUG Executing listener callback for Message 'devops jenkins list'
URL "http://dhud001:6900/apprel
requestfactory end point = api/json
_requestFactorySingle path = "http://dhud001:6900/apprel/api/json
RES =[object Object]
BODY =<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid URL</h2>
<hr><p>HTTP Error 400. The request URL is invalid.</p>
</BODY></HTML>

[Thu Jun 01 2017 08:21:17 GMT-0500 (Central Daylight Time)] DEBUG Sending to C58KYRMST: SyntaxError: Unexpected token < in JSON at position 0
error: no_text
Unhandled rejection Error: no_text
  at handleHttpResponse (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\lib\clients\transports\call-transport.js:105:17)
  at handleTransportResponse (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\lib\clients\transports\call-transport.js:155:19)
  at apply (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\node_modules\lodash\lodash.js:499:17)
  at wrapper (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\node_modules\lodash\lodash.js:5356:16)
  at Request.handleRequestTranportRes (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\lib\clients\transports\request.js:20:5)
  at apply (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\node_modules\lodash\lodash.js:499:17)
  at Request.wrapper [as _callback] (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\@slack\client\node_modules\lodash\lodash.js:5356:16)
  at Request.self.callback (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\request\request.js:188:22)
  at emitTwo (events.js:106:13)
  at Request.emit (events.js:191:7)
  at Request.<anonymous> (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\request\request.js:1171:10)
  at emitOne (events.js:96:13)
  at Request.emit (events.js:188:7)
  at IncomingMessage.<anonymous> (C:\Users\mcs023\WORK\DevOps\ChatOps\wrkspace\apprel\node_modules\request\request.js:1091:12)
  at IncomingMessage.g (events.js:291:16)
  at emitNone (events.js:91:20)
  at IncomingMessage.emit (events.js:185:7)
  at endReadableNT (_stream_readable.js:974:12)
  at _combinedTickCallback (internal/process/next_tick.js:80:11)
  at process._tickCallback (internal/process/next_tick.js:104:9)
zack-hable commented 6 years ago

Hi @mchennamsetty, Thanks for the error report. Since things have changed quite a bit, could you try the latest version and confirm if you're receiving the same issue?

zack-hable commented 6 years ago

Due to inactivity I will be closing this issue, if you experience this again please feel free to reopen this issue.

j-chao commented 5 years ago

Hi, I'm still having this issue with version 1.2.2, any ideas as to this issue?

zack-hable commented 5 years ago

Last I checked this plugin seemed to work correctly. Could you attach any output you received, steps that led to the error and versions of software you're using (Node.js, Jenkins, etc)?