-
Task
-
Resolution: Fixed
-
Major
-
None
-
-
arctic, tasman, frank, tethys
Prefetch and embed the Run object on the Run Details page.
Process should be to create a RESTFetchPreloader implementation that checks the current url to see if it links to a pipeline run details page and adds the Run object data if it is. See PipelineStatePreloader.
In Scope
- This data is attached to the $.blueOceanConfig object
- When the page loads the data is injected into the store
- We never have to do a XHR when loading the run details
- depends on
-
-
- Closed
-
- is related to
-
-
- Open
-
[JENKINS-40487] OPTIMIZATION: Pre-load Run data on fresh load of the Run Details
| Epic Link | New: JENKINS-37957 [ 174099 ] |
| Link |
New:
This issue depends on |
| Description |
Original:
On a fresh load of the run details we want to avoid fetching the pipeline's run. Note: What we're talking about here is when the user goes directly to the Run Details page e.g. from a notification of some sort (e.g. an email). We're not talking about "normal" navigation to the Run Details page. *In Scope* * This data is attached to the {{$.blueOceanConfig}} object * When the page loads the data is injected into the store * We never have to do a XHR when loading the run details |
New:
Prefetch and embed the Run object on the Run Details page. Process should be to create a [RESTFetchPreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/RESTFetchPreloader.java] implementation that checks the current url to see if it links to a pipeline run details page and adds the Run object data if it is. See [PipelineStatePreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/java/io/jenkins/blueocean/preload/PipelineStatePreloader.java]. |
| Description |
Original:
Prefetch and embed the Run object on the Run Details page. Process should be to create a [RESTFetchPreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/RESTFetchPreloader.java] implementation that checks the current url to see if it links to a pipeline run details page and adds the Run object data if it is. See [PipelineStatePreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/java/io/jenkins/blueocean/preload/PipelineStatePreloader.java]. |
New:
Prefetch and embed the Run object on the Run Details page. Process should be to create a [RESTFetchPreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-commons/src/main/java/io/jenkins/blueocean/commons/RESTFetchPreloader.java] implementation that checks the current url to see if it links to a pipeline run details page and adds the Run object data if it is. See [PipelineStatePreloader|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/java/io/jenkins/blueocean/preload/PipelineStatePreloader.java]. *In Scope* * This data is attached to the {{$.blueOceanConfig}} object * When the page loads the data is injected into the store * We never have to do a XHR when loading the run details |
| Attachment | New: blueocean #528 2016-12-16 13-27-48.png [ 35200 ] |
| Sprint | Original: arctic, tasman, frank [ 131, 136, 156 ] | New: arctic, tasman, frank, christmas [ 131, 136, 156, 176 ] |
| Sprint | Original: arctic, tasman, frank, christmas [ 131, 136, 156, 176 ] | New: arctic, tasman, frank, tethys [ 131, 136, 156, 161 ] |
| Rank | New: Ranked higher |
tfennelly I think we might have to prefetch the Pipeline that the run belongs to as well as the run. See screenshot.