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

On Release of a Version recieve a Null Pointer exception

    XMLWordPrintable

Details

    Description

      After upgrading from Jenkins 2.107 and Jira Plugin 2.5 when executing the Release A Version step in a Jenkins job the output simply states:

      [JIRA] Marking version <foo> in project <bar> as released.
      FATAL: Unable to release jira version <foo>/<bar>: java.lang.NullPointerException
      Finished: FAILURE

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          View 4 older comments
          warden Radek Antoniuk added a comment -

          I was able to re-produce the NPE on a plain Jenkins instance that had no JIRA site defined in the Global settings. Can you try the following:

          • go to Global configuration and ensure connectivity to JIRA with the Validate button? (then Save configuration and re-run the build)
          • if that doesn't help, can you try removing and re-adding the JIRA site? 
          warden Radek Antoniuk added a comment - I was able to re-produce the NPE on a plain Jenkins instance that had no JIRA site defined in the Global settings. Can you try the following: go to Global configuration and ensure connectivity to JIRA with the Validate button? (then Save configuration and re-run the build) if that doesn't help, can you try removing and re-adding the JIRA site? 
          vilppuvuorinen Vilppu Vuorinen added a comment -

          Validate prints out a success. I tried recreating the site config, but I don't have a test project for validating this. I'll have to get back to this after there is an actual release build.

          It looks like the config format was changed in 3.0.7 as I could not roll back to 3.0.6 without losing site config. It sure looks like everything is pointing back to the site config.

          vilppuvuorinen Vilppu Vuorinen added a comment - Validate prints out a success. I tried recreating the site config, but I don't have a test project for validating this. I'll have to get back to this after there is an actual release build. It looks like the config format was changed in 3.0.7 as I could not roll back to 3.0.6 without losing site config. It sure looks like everything is pointing back to the site config.
          vilppuvuorinen Vilppu Vuorinen added a comment -

          Looks like deleting the site config and creating it again fixed the issue. It sounds like config migration breaking existing configs.

          vilppuvuorinen Vilppu Vuorinen added a comment - Looks like deleting the site config and creating it again fixed the issue. It sounds like config migration breaking existing configs.
          vilppuvuorinen Vilppu Vuorinen added a comment -

          After a single successful release the issue has resurfaced. I've now rolled back to 3.0.6 hoping I could get the releases rolling again.

          vilppuvuorinen Vilppu Vuorinen added a comment - After a single successful release the issue has resurfaced. I've now rolled back to 3.0.6 hoping I could get the releases rolling again.
          olamy Olivier Lamy added a comment -

          should be fixed by https://github.com/jenkinsci/jira-plugin/pull/192

          olamy Olivier Lamy added a comment - should be fixed by https://github.com/jenkinsci/jira-plugin/pull/192

          People

            olamy Olivier Lamy
            genei_09 Aaron Sua
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: