Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
Description
I am trying to configure the JIRA plugin with Jenkins but I am receiving the error "This is a valid URL but it doesn't look like JIRA". I am trying to connect to my company installation of JIRA studio which is http://fantasticthinking.jira.com and I know this URL is correct as I have several projects using it successfully.
Attachments
Activity
Mandeep Rai
added a comment - I found the following link, which helped me to solve this problem:
http://stackoverflow.com/questions/6585632/configuring-the-atlassian-jira-plugin-to-work-with-jenkins-ci-system I'm seeing this with "Atlassian JIRA v6.0-OD-11" (Atlassian OnDemand JIRA), Jenkins 1.513, and Jenkins JIRA plugin version 1.35. I tried the workaround in the stackoverflow post mentioned above but it didn't work for me.
One more data point: even though the error message appears on the /configure page, Jenkins is actually able to hit JIRA's API and update issues, adding comments and commits.
Adam Monsen
added a comment - - edited I'm seeing this with "Atlassian JIRA v6.0-OD-11" (Atlassian OnDemand JIRA), Jenkins 1.513, and Jenkins JIRA plugin version 1.35. I tried the workaround in the stackoverflow post mentioned above but it didn't work for me.
One more data point: even though the error message appears on the /configure page, Jenkins is actually able to hit JIRA's API and update issues, adding comments and commits. Adam Monsen
added a comment - olamy, Would you mind taking a peek at this? Previously indeed the plugin was searching for text "Atlassian JIRA". The version 2.0 of the plugin switched to REST API and so this should happen no more...
I also have the same issue! This may be a problem with hosted jira installs as opposed to self-hosted installs (hence the *.jira.com address)