[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade

41 views
Skip to first unread message

jasmin.boersig@abas.de (JIRA)

unread,
Sep 9, 2019, 7:50:03 AM9/9/19
to jenkinsc...@googlegroups.com
Jasmin Börsig created an issue
 
Jenkins / Bug JENKINS-59280
jiraJqlSearch Error Message: null value after upgrade
Issue Type: Bug Bug
Assignee: Naresh Rayapati
Components: jira-steps-plugin
Created: 2019-09-09 11:49
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)
Priority: Major Major
Reporter: Jasmin Börsig

After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch e.g.

project = "ESDK1" AND "Request Type" = "ESDK App Submittal (ESDK1)" AND summary ~ "aebap-0.0.1-2018"

or even only

project = "ESDK"

now runs into the following error: 
21:30:20  Error Code: -1
21:30:20  Error Message: null value
After Upgrading, we had to enter JIRA username and API token for Authentication 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='ESDK1'%20AND%20'Request%20Type'='ESDK%20App%20Submittal%20(ESDK1)'%20AND%20summary~'aebap-0.0.1-2018'"

Downgrading to jira-steps-plugin version 1.4.5 resolved the problem.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

jasmin.boersig@abas.de (JIRA)

unread,
Sep 9, 2019, 7:51:02 AM9/9/19
to jenkinsc...@googlegroups.com
Jasmin Börsig updated an issue
Change By: Jasmin Börsig
After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch e.g.
{code:java}
project = "ESDK1" AND "Request Type" = "ESDK App Submittal (ESDK1)" AND summary ~ "aebap-0.0.1-2018" {code}
or even only
{code:java}
project = "ESDK" {code}

now runs into the following error: 
{code:java}
21:30:20  Error Code: -1
21:30:20  Error Message: null value {code}
After Upgrading, we had to enter JIRA username and API token for Authentication again. However, jirasearch still does not work. 

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

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

jasmin.boersig@abas.de (JIRA)

unread,
Sep 9, 2019, 8:00:11 AM9/9/19
to jenkinsc...@googlegroups.com
Jasmin Börsig updated an issue
After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch e.g.
{code:java}
project = "ESDK1" AND "Request Type" = "ESDK App Submittal (ESDK1)" AND summary ~ "aebap-0.0.1-2018" {code}
or even only
{code:java}
project = "ESDK" {code}
now runs into the following error: 
{code:java}
21:30:20  Error Code: -1
21:30:20  Error Message: null value {code}
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:
{code:java}
curl -u <user>:<token> "https://<company>.atlassian.net/rest/api/2/search?jql=project='ESDK1'%20AND%20'Request%20Type'='ESDK%20App%20Submittal%20(ESDK1)'%20AND%20summary~'aebap-0.0.1-2018'" {code}
Downgrading to jira-steps-plugin version 1.4.5 resolved the problem.

jasmin.boersig@abas.de (JIRA)

unread,
Sep 9, 2019, 8:01:02 AM9/9/19
to jenkinsc...@googlegroups.com
Jasmin Börsig updated an issue
After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch e.g.
{code:java}
project = "ESDK1" AND "Request Type" = "ESDK App Submittal (ESDK1)" AND summary ~ "aebap-0.0.1-2018" {code}
or even only
{code:java}
project = "ESDK" {code}
now runs into the following error: 
{code:java}
21:30:20  Error Code: -1
21:30:20  Error Message: null value {code}
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:
{code:java}
curl -u <user>:<token> "https://<company>.atlassian.net/rest/api/2/search?jql=project='ESDK1'%20AND%20'Request%20Type'='ESDK%20App%20Submittal%20(ESDK1)'%20AND%20summary~'aebap-0.0.1-2018'" {code}
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.  

jasmin.boersig@abas.de (JIRA)

unread,
Sep 9, 2019, 8:02:04 AM9/9/19
to jenkinsc...@googlegroups.com
Jasmin Börsig updated an issue
After upgrading from jira-steps-plugin 1.4.5 to 1.5.0, any previously working jqlsearch e.g.
{code:java}
project = "ESDK1" AND "Request Type" = "ESDK App Submittal (ESDK1)" AND summary ~ "aebap-0.0.1-2018" {code}
or even only
{code:java}
project = "ESDK" {code}
  
now runs into the following error: 

{code:java}
21:30:20  Error Code: -1
21:30:20  Error Message: null value {code}
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:
{code:java}
curl -u <user>:<token> "https://<company>.atlassian.net/rest/api/2/search?jql=project=' ESDK1 <key> ' %20AND%20'Request%20Type'='ESDK%20App%20Submittal%20(ESDK1)'%20AND%20summary~'aebap-0.0.1-2018' " {code}

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.  

tao.zhang@nasdaq.com (JIRA)

unread,
Sep 11, 2019, 12:47:02 AM9/11/19
to jenkinsc...@googlegroups.com
Tao Zhang commented on Bug JENKINS-59280
 
Re: jiraJqlSearch Error Message: null value after upgrade

I have experienced the same issue after upgrading to 1.5.0

Jenkins version: 2.184

Jira-steps-plugin: 1.5.0

Jenkins Master node is running inside jenkins/jenkins:2.184-centos container

[Pipeline] jiraJqlSearch
JIRA: Site - acme- Search JQL: project = 'acme' startAt: 0 maxResults: 1000
Error Code: -1
Error Message: null value

 

naresh.rayapati@gmail.com (JIRA)

unread,
Sep 16, 2019, 2:41:04 PM9/16/19
to jenkinsc...@googlegroups.com

Sorry to hear that... I will look into this soon, probably I am guessing we need to make fields as optional, mean don't even send it when it is not present.

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 2, 2019, 3:19:03 PM10/2/19
to jenkinsc...@googlegroups.com

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 3, 2019, 5:37:06 AM10/3/19
to jenkinsc...@googlegroups.com
Naresh Rayapati started work on Bug JENKINS-59280
 
Change By: Naresh Rayapati
Status: Open In Progress

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 3, 2019, 5:37:06 AM10/3/19
to jenkinsc...@googlegroups.com
Change By: Naresh Rayapati
Status: In Progress Review

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 3, 2019, 5:38:04 AM10/3/19
to jenkinsc...@googlegroups.com
 
Re: jiraJqlSearch Error Message: null value after upgrade

Merged and released with 1.5.1, should be available in update center soon.

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 3, 2019, 5:38:06 AM10/3/19
to jenkinsc...@googlegroups.com
Change By: Naresh Rayapati
Status: In Review Closed
Resolution: Fixed

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 3, 2019, 5:38:06 AM10/3/19
to jenkinsc...@googlegroups.com

benjamin.kihm@scheer-group.com (JIRA)

unread,
Oct 21, 2019, 8:05:07 AM10/21/19
to jenkinsc...@googlegroups.com
Benjamin Kihm reopened an issue
 

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: -1Error 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)
Change By: Benjamin Kihm
Resolution: Fixed
Status: Closed Reopened

benjamin.kihm@scheer-group.com (JIRA)

unread,
Oct 21, 2019, 8:06:05 AM10/21/19
to jenkinsc...@googlegroups.com
We have still the issue with jira-steps-plugin 1.5.1:
{code:java}

[Pipeline] jiraGetFields[Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields.Error Code: -1Error 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)
{code}

benjamin.kihm@scheer-group.com (JIRA)

unread,
Oct 21, 2019, 8:07:05 AM10/21/19
to jenkinsc...@googlegroups.com
Benjamin Kihm edited a comment on Bug JENKINS-59280
We have still the issue with jira-steps-plugin 1.5.1:
{code:java}
[Pipeline] jiraGetFields
[Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields.
Error Code: - 1Error 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)
{code}

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 23, 2019, 9:10:02 PM10/23/19
to jenkinsc...@googlegroups.com

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/

naresh.rayapati@gmail.com (JIRA)

unread,
Oct 28, 2019, 11:14:04 AM10/28/19
to jenkinsc...@googlegroups.com
Naresh Rayapati closed an issue as Fixed
 
Change By: Naresh Rayapati
Status: Reopened Closed
Resolution: Fixed

benjamin.kihm@scheer-group.com (JIRA)

unread,
Oct 28, 2019, 11:18:06 AM10/28/19
to jenkinsc...@googlegroups.com

benjamin.kihm@scheer-group.com (JIRA)

unread,
Oct 28, 2019, 11:20:03 AM10/28/19
to jenkinsc...@googlegroups.com
Benjamin Kihm edited a comment on Bug JENKINS-59280
[~nrayapati]

I upgraded from 1.4.5 to 1.5.1 directly.


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

benjamin.kihm@scheer-group.com (JIRA)

unread,
Nov 8, 2019, 3:51:03 AM11/8/19
to jenkinsc...@googlegroups.com
Benjamin Kihm reopened an issue
 

The problem still exists see above.
Change By: Benjamin Kihm
Resolution: Fixed
Status: Closed Reopened

naresh.rayapati@gmail.com (JIRA)

unread,
Jan 28, 2020, 10:43:03 PM1/28/20
to jenkinsc...@googlegroups.com
Naresh Rayapati commented on Bug JENKINS-59280
 
Re: jiraJqlSearch Error Message: null value after upgrade

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

naresh.rayapati@gmail.com (JIRA)

unread,
Jan 28, 2020, 10:43:04 PM1/28/20
to jenkinsc...@googlegroups.com
Naresh Rayapati closed an issue as Fixed
Change By: Naresh Rayapati
Status: Reopened Closed
Resolution: Fixed

naresh.rayapati@gmail.com (JIRA)

unread,
Jan 28, 2020, 10:44:04 PM1/28/20
to jenkinsc...@googlegroups.com
Naresh Rayapati updated an issue
Change By: Naresh Rayapati
Attachment: Screen Shot 2020-01-28 at 9.43.11 PM.png

naresh.rayapati@gmail.com (JIRA)

unread,
Jan 28, 2020, 10:44:05 PM1/28/20
to jenkinsc...@googlegroups.com
Naresh Rayapati edited a comment on Bug JENKINS-59280
 
Re: jiraJqlSearch Error Message: null value after upgrade
[~bkihm] 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


!Screen Shot 2020-01-28 at 9.43.11 PM.png|thumbnail!
Reply all
Reply to author
Forward
0 new messages