|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
It's there because it's a form action for the UI. There's nothing that can be done about that.
If it's not documented as being part of the supported API (i.e. intended to be used programmatically), you're on your own.
Even if it were documented as API (triggering builds comes to mind), there's no inconsistency: You get data from Jenkins by accessing (object)/api/xml or (object)/api/json and you perform actions using (object)/(action). Two different schemes for two different kinds of behavior.