I’m having trouble setting up the Jenkins JIRA integration and getting a weird error message.
When I try to connect Jenkins to our corporate JIRA instance, I keep getting this error:
“This is a valid URL but it doesn’t look like JIRA”
Our JIRA setup is hosted at https://[ourcompany].jira.com and I’m confident the URL is right because other tools connect to it just fine. I’ve double-checked the address multiple times.
Does anyone know if there are specific configuration options in JIRA that need to be turned on for Jenkins connectivity? Maybe some API settings or permissions that I’m missing?
Any help would be appreciated since this is blocking our CI pipeline setup.
yea, i had that prob too! try adding /rest/api/2/serverInfo at the end of your JIRA URL in Jenkins settings. the plugin might require that API endpoint for validation to work correctly.
Had this same problem last month with our Jenkins setup. It’s usually an auth issue, not the URL. Stop using your regular password - JIRA killed basic auth for most stuff. Go to your JIRA profile settings and generate a new API token. In Jenkins, use your email as the username with that token. Also double-check your JIRA account permissions. You need access to project data and the ability to create/update issues. The ‘Browse Projects’ permission is key - without it, the plugin can’t validate the connection.
Check if your JIRA instance has network restrictions or firewall rules blocking Jenkins. Corporate environments often whitelist specific IPs for API access. I hit this exact error when our security team restricted external JIRA connections without telling anyone. The URL was right, but Jenkins couldn’t talk to JIRA’s API endpoints. Contact your IT team - make sure the Jenkins server IP can access JIRA’s REST API. Sometimes it connects but fails during the plugin’s validation because of these restrictions.