Issue Type: Improvement Improvement
Assignee: Unassigned
Components: core
Created: 30/Jul/14 11:23 PM
Description:

the endpoint prefix is sometimes inconsistent even when we deal with the same class/object

for example, the /computer object. To get the information on /computer, you normally invoke the restful call like this:

https://jenkins.mydomain.com/computer/foobar/api/json

To take it offline

https://jenkins.mydomain.com/computer/foobar/toggleOffline?offlineMessage="taking it disconnected via jenkins.go as part of the maintenance"

But when we are talking about writing restful api lib for Jenkins and the endpoint inconsistency is making developers writing case-by-case basis. And could very well end up with something broken without printing verbose message in the log:

https://jenkins.mydomain.com/computer/foobar/toggleOffline?offlineMessage="taking it disconnected via jenkins.go as part of the maintenance"/api/json

Project: Jenkins
Priority: Major Major
Reporter: Sam Xiao
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.

Reply via email to