-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.230-2.263
Plugin 3.1.0-3.2
updating from 3.0.18 to 3.1.0, 'Update relevant issues' makes the build fail with error:
[Jira] The system configuration does not allow remote Jira access
The configuration (in Jenkins and in the job) didn't change and before the update it worked correctly.
Logging of 'hudson.plugins.jira':
Jun 17, 2020 10:57:15 AM FINE hudson.plugins.jira.selector.DefaultIssueSelectorLooking for Jira ID in AB-1234 : jira commit message test Jun 17, 2020 10:57:20 AM FINE hudson.plugins.jira.JiraChangeLogAnnotatorUsing site: [SITE URL] Jun 17, 2020 10:57:20 AM FINE hudson.plugins.jira.JiraChangeLogAnnotatorUsing issue pattern: ([a-zA-Z][a-zA-Z0-9_]+-[1-9][0-9]*)([^.]|\.[^0-9]|\.$|$) Jun 17, 2020 10:57:20 AM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotateNo known Jira project corresponding to id: 'AB-1234'
- is caused by
-
JENKINS-64083 jira-plugin does not use global credentials anymore
- Closed
- relates to
-
JENKINS-49330 JIRA Update relevant issues failing
- Closed
-
JENKINS-43980 Issue Field Updater unable to assign Jenkins env variable in field value for custom field id
- Closed