Using the plugin I ran into a couple of issues. First it doesn't allow you to connect to a secure Jenkins server, would be nice if that got added.
In any event once I got the security part worked out I now get a 404 error. I looked at the source to see what the url is that it tries to use and if I construct a similar one it will work from the browser.
The URL it looked like it was using is something like this:
http://jenkins_server/job/JobName/api/json?nocache=somegeneratednumber
I ran that without the nocache setting and it works fine but when I try using it in the plugin I get the 404 error.
In the plugin I put the URL in as http://jenkins_server/
While putting the Job Name in the field it's required in.
Also I do have my Jira server setup with whitelist entry and my browsers have the sites on their trusted lists in case anyone is thinking along those lines.
Thanks,
J
Found the problem. The Jenkins logs were not ending up where I thought they were via the web links. Once I pointed to the correct path all worked.
Never mind, just worked it out. I specified a FQDN eg. "my-server.internal.domain.com" in both the gadget and the whitelist.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you able to add any more detail? I have the same (or similar) problem.
Before whitelisting my-server I get:
Build status loading error: failed to parse JSON Response content: Requests to http://my-server/job/MyProject/api/json?nocache=136633125 are
not allowed. See your administrator about configuring a whitelist entry for this destination
(http://confluence.atlassian.com/x/KQfCDQ ).
After whitelisting my-server I get:
Build status loading error: failed to parse JSON Response content: Host Not Found DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection. Please check that the host name has been spelled correctly.
The first instance appears in the JIRA log, the second is not shown at all in the log.
What was the 'correct path' you identified?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.