-
Bug
-
Resolution: Unresolved
-
Minor
When fetching updated runs since the last fetch cycle, the /runs API will fetch the run matching the "since" parameter, not just ones after that. This means extra data is sent every time, extra CPU/network hit.
Trivial change here: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java#L121
The catch is we need to ensure tests handle this correctly, and the UI does too. Possible issues of API compat, but I think likely safe.
- links to
[JENKINS-37234] Stage view fetches one extra run when supplying a "since" parameter
Description |
Original:
When fetching updated runs since the last fetch cycle, the /runs API will fetch the run matching the "since" parameter, not just ones after that. This means extra data is sent every time. Trivial change here: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java#L121 The catch is we need to ensure tests handle this correctly, and the UI does too. Possible issues of API compat, but I think likely safe. |
New:
When fetching updated runs since the last fetch cycle, the /runs API will fetch the run matching the "since" parameter, not just ones after that. This means extra data is sent every time, extra CPU/network hit. Trivial change here: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java#L121 The catch is we need to ensure tests handle this correctly, and the UI does too. Possible issues of API compat, but I think likely safe. |
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Labels | Original: performance | New: hold performance |
Remote Link | New: This issue links to "CloudBees Internal OSS-1541 (Web Link)" [ 18657 ] |
Labels | Original: hold performance | New: hold performance triaged-2018-11 |
Assignee | Original: Sam Van Oort [ svanoort ] |