[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers updated JENKINS-37519 Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers updated JENKINS-37519 Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-37519
Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Change By:
Cliff Meyers
The "fetch" library should allow for Capabilities metadata to be fetched after a standard REST API call is made, so a unified view of the data can be returned to the UI component layer.Need to design a configuration that can be passed to fetch to indicate which graph paths in the response should be used for fetching capabilities.e.g. for the following response{code}[{ name: 'pipeline', _class: 'io.jenkins.blueocean.rest.model.PipelineImpl' },{ name: 'freestyle', _class: 'io.jenkins.blueocean.rest.model.AbstractPipelineImpl }]{code}we need a way to express that the top-level "_class" property should be fetched. Perhaps GraphQL can be used as an inspiration for this if not outright implementation.The augmented response would look like:{code}[{ name: 'pipeline', _class: 'io.jenkins.blueocean.rest.model.PipelineImpl', _capabilities: [ 'foo.bar.Thing' ] },{ name: 'freestyle', _class: 'io.jenkins.blueocean.rest.model.AbstractPipelineImpl, _capabilities: [ 'foo.bar.OtherThing' ] }]{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Change By: James Dumay Sprint: 1.0-beta-1 , 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers started work on JENKINS-37519 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Pulling this forward because in order to fix JENKINS-37831 we need more capabilities logic, and we need to handle this more cleanly. Change By: Cliff Meyers Sprint: 1.0-beta- 2 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Change By: James Dumay Sprint: 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-37519
Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Issue Type:
Task
Assignee:
Cliff Meyers
Components:
blueocean-plugin
Created:
2016/Aug/18 3:27 PM
Priority:
Minor
Reporter:
Cliff Meyers
The "fetch" library should allow for Capabilities metadata to be fetched after a standard REST API call is made, so a unified view of the data can be returned to the UI component layer. Need to design a configuration that can be passed to fetch to indicate which graph paths in the response should be used for fetching capabilities. e.g. for the following response
[
{ name: 'pipeline', _class: 'io.jenkins.blueocean.rest.model.PipelineImpl' },
{ name: 'freestyle', _class: 'io.jenkins.blueocean.rest.model.AbstractPipelineImpl }
]
we need a way to express that the top-level "_class" property should be fetched. Perhaps GraphQL can be used as an inspiration for this if not outright implementation. The augmented response would look like:
[
{ name: 'pipeline', _class: 'io.jenkins.blueocean.rest.model.PipelineImpl', _capabilities: 'foo.bar.Thing' },
{ name: 'freestyle', _class: 'io.jenkins.blueocean.rest.model.AbstractPipelineImpl, _capabilities: 'foo.bar.OtherThing' }
]
