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

2020-04-17 Thread linuxsu...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick commented on  JENKINS-61954  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /runs/ REST api failing to return after update to Jenkins 2.222.1   
 

  
 
 
 
 

 
 /runs/?start=0=85 is not belong to pipeline-restful-api-plugin I believe  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205836.1587155449000.13485.1587174360187%40Atlassian.JIRA.

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

2020-04-17 Thread killsp...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Fenton-Garcia created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61954  
 
 
  /runs/ REST api failing to return after update to Jenkins 2.222.1   
 

  
 
 
 
 

 
Issue Type: 
  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  
 
 
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=85 which worked perfectly fine until upgrading. Now we have to use /runs/?start=0=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.