Jenkins-API
view release on metacpan or search on metacpan
The information can be refined in the same way as "current_status"
using extra_params.
view_status
Provides the status of the specified view. The list of views is
provided in the general status report.
$jenkins->view_status('MyView');
# {
# 'busyExecutors' => {},
# 'queueLength' => {},
# 'totalExecutors' => {},
# 'totalQueueLength' => {}
# }
# {
# 'description' => undef,
# 'jobs' => [
# {
# 'color' => 'blue',
# 'name' => 'Test',
The method will die saying 'Invalid response' if the server doesn't
respond as it expects, or die with a JSON decoding error if the JSON
parsing fails.
load_statistics
This returns the load statistics for the server.
$jenkins->load_statistics();
# {
# 'busyExecutors' => {},
# 'queueLength' => {},
# 'totalExecutors' => {},
# 'totalQueueLength' => {}
# }
This also allows the same extra_params as the "current_status" call.
The depth and tree parameters work in the same way. See the Jenkins API
documentation for more details.
The method will die saying 'Invalid response' if the server doesn't
lib/Jenkins/API.pm view on Meta::CPAN
The information can be refined in the same way as L</current_status> using C<extra_params>.
=head2 view_status
Provides the status of the specified view. The list of views is
provided in the general status report.
$jenkins->view_status('MyView');
# {
# 'busyExecutors' => {},
# 'queueLength' => {},
# 'totalExecutors' => {},
# 'totalQueueLength' => {}
# }
# {
# 'description' => undef,
# 'jobs' => [
# {
# 'color' => 'blue',
# 'name' => 'Test',
lib/Jenkins/API.pm view on Meta::CPAN
The method will die saying 'Invalid response' if the server doesn't
respond as it expects, or die with a JSON decoding error if the JSON
parsing fails.
=head2 load_statistics
This returns the load statistics for the server.
$jenkins->load_statistics();
# {
# 'busyExecutors' => {},
# 'queueLength' => {},
# 'totalExecutors' => {},
# 'totalQueueLength' => {}
# }
This also allows the same C<extra_params> as the L</current_status> call. The
depth and tree parameters work in the same way. See the Jenkins
API documentation for more details.
The method will die saying 'Invalid response' if the server doesn't
t/live-query.t view on Meta::CPAN
'Client-Response-Num',
1,
'X-Content-Type-Options',
'nosniff',
'X-Jenkins',
'2.60.3',
'X-Jenkins-Session',
'c70f6e5a'
],
'content' =>
'{"_class":"hudson.model.OverallLoadStatistics","availableExecutors":{},"busyExecutors":{},"connectingExecutors":{},"definedExecutors":{},"idleExecutors":{},"onlineExecutors":{},"queueLength":{},"totalExecutors":{},"totalQueueLength":{}}',
'msg' => 'OK',
'code' => '200'
}
},
{
'res' => {
'msg' => 'OK',
'code' => '200',
'content' => '<?xml version=\'1.0\'?>
<project>
( run in 0.325 second using v1.01-cache-2.11-cpan-87723dcf8b7 )