-
Notifications
You must be signed in to change notification settings - Fork 1.9k
list-jira-bugs.coffee Returns no data #1173
Comments
2013-10-08T00:34:49.822604+00:00 app[web.1]: TypeError: Cannot call method 'split' of undefined |
What version of hubot-scripts are you using? Should be in package.json. Also, what are specifically saying, expecting hubot to respond? I seem to recall some updates to this recently. |
"hubot-scripts": ">= 2.5.6", There are a number of bugs in our projects, some are assigned to me others are general. I checked the URL's manually and it returned a bunch of data, so it appears to be good on JIRA's end. |
@darksheer when I say this, I mean I'm not really familiar with these particular jira scripts. I'm asking for specific text, so I can compare to the regex that's in the script to help you diagnose the error. From what I can see here, and the initial report, you are doing like "hubot list my issues". Please correct me if I'm wrong.
The error is calling 'split' on something not defined. There's only two places split gets called:
The first is splitting out the user's email, which comes from Jira, so it's probably not that. The second is splitting something from the environment, which could feasibly be undefined. You didn't mention the environment in question, Can you try setting the following please?
|
Tried setting to this: HUBOT_JIRA_ISSUES_TYPES="bug|task|sub task|support ticket|new feature|epic" Even tried selecting only 'bug' Still no returned data. |
@technicalpickles Updated the HUBOT_JIRA_ISSUE_PRIORITIES="blocker|high|medium|minor|trivial" as well just to make sure, still no data returned. I did get the other Jira script working, which shares some of the same config vars (username / password), there is something else 'missing'. The other script does do some 'weirdness' with not returning data sets consistently: |
Messed around all morning adjusting the VARs, still nothing. Is there some other log file other than heroku logs I can investigate ? |
No, that would be it. I would also suggest trying to run your hubot locally with the environment variables you've set, to see if you can reproduce that in the shell adapter. If you can, you can copy hubot-script's list-jira-issues into your own scripts/ directory to add more debugging and error checking /cc @crcastle (the original contributor) I really could use someone to take over maintaing this and the other jira scripts as external packages if anyone is interested /cc #1113 |
Played around a ton with this, still couldn't get anything working properly. Not sure what to do next outside of chopping up some of the code. Was hoping @crcastle was gonna chime in. |
cc hubotio/hubot#644 for making sure errors get logged |
Installed and configured list-jira-bugs.coffee
Set vars:
HUBOT_JIRA_DOMAIN=ourdomain.atlassian.net
HUBOT_JIRA_PASSWORD='password@#$#@$@#$@#'
HUBOT_JIRA_USER='MEEEEEEE'
Hubot comes online and I can invode the list bugs, Hubot returns with Searching for issues.
heroku logs provides no insight as to what might be causing a failure. I did verify that all the URL / paths that the code is looking for exist and work.
Not sure what the proper troubleshooting steps are.
The text was updated successfully, but these errors were encountered: