-
Bug
-
Resolution: Not A Defect
-
Major
-
None
We use the JIRA plugin only for updating the tickets with the build results. At some point, this stopped working, the only messages being in the build logs
XX-111 issue doesn't exist in JIRA
The builds do not fail because of this (which is good).
From the JIRA logs, it looks like the plugin is not trying to authenticate to JIRA.
When clicking on "Validate Settings", what I'm seeing in the JIRA http-dump log is this:
127.0.0.1 o692x983x5 - [24/May/2018:11:32:14 +0000] "GET https://<mysite>/jira/rest/api/latest/mypermissions HTTP/1.1" 200 14127 0.0500 - "Atlassian HttpClient 0 .23.0 / Atlassian JIRA Rest Java Client-unknown (0) / Default" - ___ Request _____________________________________________________ Request HTTP Headers : host=localhost:8080 accept=application/json user-agent=Atlassian HttpClient 0.23.0 / Atlassian JIRA Rest Java Client-unknown (0) / Default x-forwarded-for=redacted x-forwarded-host=redactedad x-forwarded-server=redacted connection=Keep-Alive Request Attributes : jira.xsrf.set.cookie.pending=redacted jira.request.start.millis=1527161534680 com.atlassian.jira.web.filters.pagebuilder.PageBuilderFilter_alreadyfiltered=true com.atlassian.jira.web.filters.accesslog.AccessLogFilter_already_filtered=true is_rest_request=true atlassian.core.seraph.original.url=/rest/api/latest/mypermissions jira.webwork.cleanup=false os_authTypeDefault=any com.atlassian.labs.botkiller.BotKillerFilter=true com.atlassian.jira.web.filters.johnson.JiraJohnson503Filter_already_filtered=true com.atlassian.jira.web.filters.steps.senderror.CaptureSendErrorMessageResponseWrapper_CAPTURED=OK com.atlassian.gzipfilter.GzipFilter_already_filtered=true com.newrelic.agent.TRANSACTION_NAME=/rest/api/* com.atlassian.jira.security.xsrf.XsrfTokenAdditionRequestFilter_already_filtered=true com.atlassian.jira.web.filters.JiraFirstFilter_alreadyfiltered=true page.builder=com.atlassian.jira.web.pagebuilder.DefaultPageBuilder@3480c1d3 B3-TraceId=6ef4b65157ef7a loginfilter.already.filtered=true com.atlassian.prettyurls.filter.PrettyUrlsSiteMeshFixupFilter=true jira.request.id=692x983x5 com.atlassian.jira.web.filters.JiraPostEncodingFilter_alreadyfiltered=true os_securityfilter_already_filtered=true com.atlassian.prettyurls.filter.PrettyUrlsSiteMeshFilter=true Request Data (0 bytes). ___ Response ____________________________________________________ Response HTTP Headers : X-AUSERNAME=anonymous Cache-Control=no-cache, no-store, no-transform Content-Type=application/json Response Data (total 14127 bytes) : <large json with 'no rights to do anything'>
but the settings to get validated ("Success").
Also, in JIRA user management, the user jenkins-jira shows as "Never logged in".
The JIRA user jenkin-jira is a JIRA administrator.
Jenkins 2.1.24
JIRA plugin 3.0.0, but same behavior also for 2.5.2
- is related to
-
-
- Closed
-