Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62706

After updating to 3.1.0 'Update relevant issues' stopped working

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Fixed but Unreleased (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: jira-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.230-2.263
      Plugin 3.1.0-3.2
    • Similar Issues:

      Description

      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'

        Attachments

          Issue Links

            Activity

            Hide
            f1nny Craig Finnegan added a comment - - edited

            Any update here? Or anyone know how can get someone assigned (new to jenkins Jira so not sure the flow/SOP) - this has caused pretty much all of our builds to fail for the past few months because I forget the plugin is broken when doing updates and have to go back and re-downgrade the Jira Plugin again Seems pretty serious considering it makes the plugin+jenkins builds unusable without downgrading (assuming using update issues action) 

            Or is this something where we should be re-generating the credentials in a different way? Not sure if this is only applying to existing plugin users and not new ones maybe?

            Thanks!

            Olivier Lamy Radek Antoniuk (tagging based on the wiki maintainers, maybe you guys can help! )

            Show
            f1nny Craig Finnegan added a comment - - edited Any update here? Or anyone know how can get someone assigned (new to jenkins Jira so not sure the flow/SOP) - this has caused pretty much all of our builds to fail for the past few months because I forget the plugin is broken when doing updates and have to go back and re-downgrade the Jira Plugin again Seems pretty serious considering it makes the plugin+jenkins builds unusable without downgrading (assuming using update issues action)  Or is this something where we should be re-generating the credentials in a different way? Not sure if this is only applying to existing plugin users and not new ones maybe? Thanks! Olivier Lamy Radek Antoniuk (tagging based on the wiki maintainers, maybe you guys can help! )
            Hide
            warden Radek Antoniuk added a comment -

            Craig Finnegan would you have some spare time to try to create at least a failing test-case for this behavior? (see README for some hints or just let us know if we can help)
            If not and this is critical or just painful maintenance for your company process, please consider sponsoring one of the maintainers via GitHub sponsors feature

            Show
            warden Radek Antoniuk added a comment - Craig Finnegan would you have some spare time to try to create at least a failing test-case for this behavior? (see README for some hints or just let us know if we can help) If not and this is critical or just painful maintenance for your company process, please consider sponsoring one of the maintainers via GitHub sponsors feature
            Hide
            raphael_unique Raphaël UNIQUE added a comment -

            still the same issue with v3.2.0 of the plugin

            still downgrade to 3.0.X  to fix this

            Show
            raphael_unique Raphaël UNIQUE added a comment - still the same issue with v3.2.0 of the plugin still downgrade to 3.0.X  to fix this
            Hide
            warden Radek Antoniuk added a comment -

            Since we got a PR today - thanks Kevin!, would anyone like to give it a trial with the incremental build and confirm it fixes this issue?

             

            Show
            warden Radek Antoniuk added a comment - Since we got a PR today - thanks Kevin!, would anyone like to give it a trial with the incremental build  and confirm it fixes this issue?  
            Hide
            ashishk Ashish Kulkarni added a comment -

            Radek Antoniuk I tried the incremental build and can confirm that it fixes the issue

            Show
            ashishk Ashish Kulkarni added a comment - Radek Antoniuk I tried the incremental build and can confirm that it fixes the issue

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ricktw Rick Oosterholt
              Votes:
              11 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: