Jira would be the correct site for feature requests, unless you want to e.g. discuss them or determine how big demand is. I told you in JENKINS-18349 that it's best to have a separate issue for each affected component so it actually reaches the correct developers who often only care about issues filed against their own plugins. So, if no such request exists yet, just file a new issue against `workflow-plugin` on that site.
For reference: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-Beforerequestinganimprovementorfeature On 21.12.2014, at 06:10, Kenneth Baltrinic <[email protected]> wrote: > I am not sure if this is the right place to put feature requests but I have > two closely related ones. The first is to implement support for grape in the > workflow plug-in so that external groovy libraries like http-builder can be > @grab-ed. Perhaps implementing grape support would obviate the need for this > second request in 99% of the cases, but still, it would be nice if the > cps-global-lib plugin also supported adding jar files to the library for > those occasional jars that are not in maven central, and thus can't be > grabbed via grape. > > Thoughts? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/dbcd1d07-bdca-40d4-8cd9-87616eca64e0%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/56D6B15E-00BF-41C6-AD8F-E614BF9C2EA8%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
