Uses of Package
io.jenkins.plugins.batchcontrol.action

Packages that use io.jenkins.plugins.batchcontrol.action
Package
Description
io.jenkins.plugins.batchcontrol.action
 
  • Classes in io.jenkins.plugins.batchcontrol.action used by io.jenkins.plugins.batchcontrol.action
    Class
    Description
    ActivationItem
    One activation or hold request at /batch-control/activations/<id>/ (SPEC item 6a), the URL the notifications link to: detail view plus the state-changing POST endpoints approve, reject, cancel and changeApprover, following RequestItem.
    ActivationsSection
    The activation request screen at /batch-control/activations/ (SPEC item 6a, D-66): the activation and hold requests the viewer may see as pending (those awaiting the viewer's decision marked), active (the request in effect for its job) and ended, each in pages of 50 (?pendingPage=N, ?activePage=N, ?endedPage=N).
    ActiveGrantsSection
    Routing object for /batch-control/grants/active/....
    ActiveGrantsSection.Item
    One active grant; only carries the revoke endpoint.
    ChangesSection
    The change record list at /batch-control/changes/ (SPEC item 9).
    DashboardSection
    The run record dashboard at /batch-control/dashboard/ (SPEC item 10): the most recent builds of every job with cause, user, parameters, result, duration, who aborted it, and — for APPROVED_REQUEST builds — a link to the originating run request.
    GrantRequestItem
    One grant request at /batch-control/grants/<id>/: detail view plus the five state-changing POST endpoints (approve, reject, cancel, changeApprover and, for its open window, revoke — R4-12).
    GrantsSection
    The grant screens at /batch-control/grants/ (SPEC item 8, JIT permission requests).
    GrantsSection.Row
    One row of the Grants lists: a grant request and, once approved, its permission window (the window carries the request's id).
    HistorySection
    The history browser at /batch-control/history/ (SPEC item 12): filtered listings of run records, incidents, change records and run requests, a monthly aggregate JSON endpoint, and CSV exports.
    IncidentItem
    One incident at /batch-control/incidents/<id>/ (SPEC item 11): detail view plus the four state-changing POST endpoints (acknowledge, resolve, comment, rerun).
    IncidentsSection
    The incident list at /batch-control/incidents/ (SPEC item 11).
    JobActivationNoticeAction
    The job-page Batch Control notice area: whether a run-controlled job is activated, not activated or on hold, with a link to the activation request form (SPEC item 6a), and, on an approval-required job, that manual runs need an approved run request, with a link to the request form (SPEC item 6, e2e-03 DEF-01).
    JobNoticesWidget
    The job page notices (trigger lock, approval, activation) as a card of core's new job page.
    JobTriggerLockAction
    The job-page notice for blocked unattended triggers (SPEC item 6).
    RequestItem
    One run request at /batch-control/requests/<id>/: detail view plus the four state-changing POST endpoints (approve, reject, cancel, changeApprover).
    RequestItem.RecentRun
    One row of the recent-run table.
    RequestsSection
    The run request lists at /batch-control/requests/ (D-66): pending requests (oldest first), active ones (approved, run not started) and ended ones (newest first), each in pages of 50 selected with ?pendingPage=N, ?activePage=N and ?endedPage=N.