Package io.jenkins.plugins.batchcontrol.action

package io.jenkins.plugins.batchcontrol.action
  • Classes
    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.
    BatchControlRootAction
    Global "Batch Control" page at /batch-control.
    ChangesSection
    The change record list at /batch-control/changes/ (SPEC item 9).
    ComputedFolderActivationAction
    Activation on a computed folder (multibranch project, organization folder), which carries the activation of the jobs it generates (D-46c, SPEC item 6a).
    ComputedFolderActivationActionFactory
    Attaches ComputedFolderActivationAction to every computed folder (D-46c).
    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.
    FolderCreateWindowAction
    e2e-03 DEF-19 (SPEC item 8, D-40): the folder page tells the holder of a Create window which new job names the window allows.
    FolderCreateWindowActionFactory
    Attaches FolderCreateWindowAction (e2e-03 DEF-19) and FolderGrantRequestAction (R4-14) to every folder.
    FolderGrantRequestAction
    R4-14 (D-66): the folder counterpart of JobGrantRequestAction, a "Request Change Permission" entry on a folder that opens the grant request form prefilled for the folder (scopeFullName=<folder>).
    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).
    JobActivationForm
    The activation request form at <item>/batch-control-activation/ (SPEC item 6a, D-39, D-64) for a job (JobRequestActionFactory) or a computed folder, which carries the activation of its children (D-46c, ComputedFolderActivationActionFactory).
    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).
    JobGrantRequestAction
    Sidebar entry "Request Change Permission" on a job, linking to the grant request screen with this job already filled in (U-01).
    JobNoticesWidget
    The job page notices (trigger lock, approval, activation) as a card of core's new job page.
    JobNoticesWidget.FactoryImpl
    Contributes the card to a job's widgets on the new job page only.
    JobRequestAction
    Per-job "Request Run" page at /job/<name>/batch-control/ (attached by JobRequestActionFactory).
    JobRequestActionFactory
    Attaches the plugin's two per-job sidebar entries, and the trigger-lock notice, to every job.
    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.
    RequestRunUiDecorator
    Relabels core's "Build Now" sidebar entry on approval-protected jobs (SPEC item 6: the manual build entry point must not read "Build Now" while run control is on).
    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.
    RunApprovalNoticeAction
    The build-page counterpart of the job-page approval notice (SPEC item 6, e2e re-audit DEF-31): on every build of a job whose manual runs need an approved run request, the build page says so and links the run request form for a viewer who may submit it.
    RunApprovalNoticeActionFactory
    Attaches RunApprovalNoticeAction to the builds of a job whose manual runs need an approved request (e2e re-audit DEF-31), and to no build while run control is off or the job needs no approval (S-18-06).