|
||||||||||||||
|
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 |
||||||||||||||
- [JIRA] (JENKINS-16264) Posting config.x... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)
- [JIRA] (JENKINS-16264) Posting con... [email protected] (JIRA)

This is not supposed to work I think; config.xml is for a slave. Probably accidental that the /api description page in this case mentions it.
Being able to GET/POST /config.xml (as opposed to /computer/(master)/config.xml) may well be useful, though that would be an RFE and it is complicated by the fact that Jenkins global configuration lives not just in $JENKINS_HOME/config.xml but in a number of other files as well.