Repository navigation
[JENKINS-1315] Add remote api for the '/computer' url #24114
Description
I would like to see the existing api extended to the 'http://hudson/computer/'
url. This would provide both xml and json responses to the current status of
all nodes.
My use of this api would be to drive a management dashboard to show the
online/offline status of all slave hudson connections (over 8-9 independent
hudson instances).
The data presented on the html rendered page would be sufficient:
- node name
- online/offline status
- clock difference
- architecture
Originally reported by tblack, imported from: Add remote api for the '/computer' url
- status: Closed
- priority: Major
- component(s): other
- resolution: Fixed
- resolved: 2008-03-12T21:56:31+00:00
- votes: 0
- watchers: 0
- imported: 2025-12-08
Raw content of original issue
I would like to see the existing api extended to the 'http://hudson/computer/' url. This would provide both xml and json responses to the current status of all nodes.
My use of this api would be to drive a management dashboard to show the online/offline status of all slave hudson connections (over 8-9 independent hudson instances).
The data presented on the html rendered page would be sufficient:
- node name
- online/offline status
- clock difference
- architecture
- environment:
Platform: All, OS: Linux
Activity
jenkins-infra-bot commentedon Feb 18, 2008
tblack:
Raw content of original comment:
I will take a crack at this one.
jenkins-infra-bot commentedon Feb 18, 2008
tblack:
Raw content of original comment:
Created an attachment (id=180)
api entry point
jenkins-infra-bot commentedon Feb 18, 2008
tblack:
Raw content of original comment:
Created an attachment (id=181)
exported Computer methods
jenkins-infra-bot commentedon Feb 18, 2008
tblack:
Raw content of original comment:
Created an attachment (id=182)
exported ComputerSet methods
jenkins-infra-bot commentedon Feb 18, 2008
tblack:
Raw content of original comment:
I was able to get the computer (node) data exposed, but not any of the monitor
data (clock, diskspace, architecture).
Can I can a review and feedback on the proposed solution (attached)? In
particular, I was not sure when @ExportedBean was needed versus @Exported. The
javadoc for @ExportedBean seemed to say all fields and getter methods would be
exposed, but I still had to add @Exported to the methods I wanted to publish.
jenkins-infra-bot commentedon Feb 29, 2008
Raw content of original comment:
Link back to the discussion:
http://www.nabble.com/Adding-a-remote-api-for-hudson-system-information-tt15705566.html#a15705566
jenkins-infra-bot commentedon Mar 12, 2008
tblack:
Raw content of original comment:
implemented remote api for computer nodes
jenkins-infra-bot commentedon Mar 12, 2008
tblack:
Raw content of original comment:
implemented in release 1.195