[JIRA] (JENKINS-38482) Documentation of ExtensionPoints and their binding attributes they fill pass through

[tscher...@cloudbees.com (JIRA)]

Title: Message Title

Thorsten Scherler created an issue   Jenkins / JENKINS-38482 Documentation of ExtensionPoints and their binding attributes they fill pass through Issue Type: Task Assignee: Michael Neale Components: blueocean-plugin Created: 2016/Sep/24 6:00 PM Priority: Minor Reporter: Thorsten Scherler IN https://github.com/jenkinsci/blueocean-plugin/pull/521 I take the point which leads to "contract properties" passed to certain ExtensionPoints. ATM we do it on free guess and all properties are passed through anyway. However we do not have API style declarations of extension points and the attributes we pass through. Which makes it hard for adopters to create reliable alternatives for our default implementations. I say ATM the graph is the only use case that we know of that had used run.id in a certain point of time. For housekeeping I prefer to get rid of it since it is redundant now because we pass full run. As started I see your point, but see as well the urgent need to declare ExtensionPoints as API where we can deprecate certain attributes to later drop them. ...and to document them to start with. in case you see the urge Michael Neale please assign to final implementer otherwise just close it. 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.