[JIRA] (JENKINS-61954) /runs/ REST api failing to return after update to Jenkins 2.222.1

3 views
Skip to first unread message

killspire@gmail.com (JIRA)

unread,
Apr 17, 2020, 4:31:02 PM4/17/20
to jenkinsc...@googlegroups.com
Ryan Fenton-Garcia created an issue
 
Jenkins / Bug JENKINS-61954
/runs/ REST api failing to return after update to Jenkins 2.222.1
Issue Type: Bug Bug
Assignee: Rick
Attachments: image-2020-04-17-14-30-14-354.png
Components: pipeline-restful-api-plugin
Created: 2020-04-17 20:30
Environment: Windows Server: 2016
Jenkins: 2.222.1
Labels: blueocean pipeline restFul REST
Priority: Minor Minor
Reporter: Ryan Fenton-Garcia

We have a web page we built that queries jenkins rest API's to populate some data. We used to get a list of the current running pull requests by going to the /runs/ page, but it seems like after updating to 2.222.1 that doesn't always work. 

More specifically, we used to access /runs/?start=0&limit=85 which worked perfectly fine until upgrading. Now we have to use /runs/?start=0&limit=50 or less to actually get a response back from the end point. It's also worth noting that accessing /runs/ without any parameters at all also doesn't even return.

We can also see the ton of threads from these requests that basically build, never return, and look like they aren't doing anything. 

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

linuxsuren@gmail.com (JIRA)

unread,
Apr 17, 2020, 9:46:03 PM4/17/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages