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

jiraJqlSearch Error Message: null value after upgrade

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: jira-steps-plugin
    • Labels:
      None
    • Environment:
      Jenkins version: 2.194
      Jira-steps-plugin: 1.5.0
      Amazon Linux 2 hvm x86_64 (both Jenkins master and nodes, we use AWS Spotfleet for all nodes)
    • Similar Issues:

      Description

      After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch now runs into the following error: 

      21:30:20  Error Code: -1
      21:30:20  Error Message: null value 

      After Upgrading, we had to re-enter JIRA username and API token for Authentication on the global Jenkins configuration page again. However, jirasearch still does not work. 

      Accessing JIRA via REST API using the search end point works appropriately:

      curl -u <user>:<token> "https://<company>.atlassian.net/rest/api/2/search?jql=project='<key>'" 

      Downgrading to jira-steps-plugin version 1.4.5 resolved the problem.

      We suspect a connection to https://issues.jenkins-ci.org/browse/JENKINS-57182.  

        Attachments

          Activity

          Hide
          bkihm Benjamin Kihm added a comment - - edited

          We have still the issue with jira-steps-plugin 1.5.1:

          [Pipeline] jiraGetFields
          [Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields.
          Error Code: -1
          Error Message: null
          [Pipeline] }
          [Pipeline] // scriptError when executing always post condition:hudson.AbortException at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:68) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:45) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
          
          Show
          bkihm Benjamin Kihm added a comment - - edited We have still the issue with jira-steps-plugin 1.5.1: [Pipeline] jiraGetFields [Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields. Error Code: -1 Error Message: null [Pipeline] } [Pipeline] // scriptError when executing always post condition:hudson.AbortException at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:68) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:45) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang. Thread .run( Thread .java:748)
          Hide
          nrayapati Naresh Rayapati added a comment -

          Benjamin Kihm Looks like this is a different step from what is being reported in this Jira jiraJqlSearch vs jiraGetFields 

          May I know from which version you have upgraded from? if you are upgrading from < 1.5.0 there was a non-passive change in 1.5.0 you would need to recreate sites from configure screen again.

          https://jenkinsci.github.io/jira-steps-plugin/changelog/

          Show
          nrayapati Naresh Rayapati added a comment - Benjamin Kihm Looks like this is a different step from what is being reported in this Jira jiraJqlSearch vs jiraGetFields  May I know from which version you have upgraded from? if you are upgrading from < 1.5.0 there was a non-passive change in 1.5.0 you would need to recreate sites from configure screen again. https://jenkinsci.github.io/jira-steps-plugin/changelog/
          Hide
          bkihm Benjamin Kihm added a comment - - edited

          Naresh Rayapati
          I upgraded from 1.4.5 to 1.5.1 directly.

          And yes I recreated the site configuration again but the error still exists.

          Show
          bkihm Benjamin Kihm added a comment - - edited Naresh Rayapati I upgraded from 1.4.5 to 1.5.1 directly. And yes I recreated the site configuration again but the error still exists.
          Hide
          bkihm Benjamin Kihm added a comment -

          The problem still exists see above.

          Show
          bkihm Benjamin Kihm added a comment - The problem still exists see above.
          Hide
          nrayapati Naresh Rayapati added a comment - - edited

          Benjamin Kihm I am be query fields without any issues. Please log a new JIRA if you are still facing this issue.

          JIRA Steps Plugin: 1.5.1
          Jenkins Version: 2.215

          Show
          nrayapati Naresh Rayapati added a comment - - edited Benjamin Kihm I am be query fields without any issues. Please log a new JIRA if you are still facing this issue. JIRA Steps Plugin: 1.5.1 Jenkins Version: 2.215

            People

            • Assignee:
              nrayapati Naresh Rayapati
              Reporter:
              tschasmine Jasmin Börsig
            • Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: