Hello, Let me know the best way to expose information to trigger builds from programs.
Extensible-choice-parameter plugin provides choice parameters whose choices are calculated dynamically, for example, with Groovy scripts. I received a pull request to expose those choices with @Export annotation, which allows programs retrieve choices via REST API: https://issues.jenkins-ci.org/browse/JENKINS-63786 https://github.com/jenkinsci/extensible-choice-parameter-plugin/pull/43 I'm not sure using @Export annotation is the best way as: * REST API looks expected to use to expose configurations, that is, to expose static attributes rather than calculated results. * REST API is accessible from users with Item/READ permissions. The current version of extensible-choice expose calculated values only to users with Item/BUILD or Item/CONFIGURE permissions. What's the best way to expose choices? Especially what I want to know are: * Does Jenkins provide alternate interface to expose parameter information to trigger builds for programmatic consumption? * Is there a way to add API for build parameter definitions of jobs? I know that a model object exposed with URL path/to/model can provide a new URL path/to/model/foo by creating a new method `doFoo()`, but there look no URLs for parameter definitions of jobs. Regards, Ikedam. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/8930b78e-3cb4-4a70-82d3-26d218bee4adn%40googlegroups.com.
