Package io.jenkins.plugins.batchcontrol.ops


package io.jenkins.plugins.batchcontrol.ops
  • Class
    Description
    One-time upgrade seeding of activation approval (SPEC item 6a, DESIGN-ACTIVATION-APPROVAL section 6): jobs that exist when this version is first installed are recorded as activated, so installing or upgrading never stops an existing schedule.
    Extension point receiving Batch Control request events (SPEC item 13, D-36).
    "Change control is on, but the installed authorization strategy is not a Batch Control strategy" (D-35a, ARCHITECTURE section 4).
    Warns administrators when change control cannot actually control changes (SPEC item 8): change control is on, but either the global authorization strategy is not a Batch Control strategy (so grants can never apply, D-35a), or some known non-admin user holds Item/Configure, Item/Create, Item/Delete or Item/Move (D-59) directly from the strategy — a standing change permission that bypasses the JIT grant process.
    One user or group that holds Item/Configure, Item/Create or Item/Delete from the authorization strategy itself, outside any grant (e2e-03 DEF-07).
    Periodic status refresh for expiry (SPEC items 7 and 8).
    The single entry point for every Incident lifecycle operation (SPEC item 11, D-10, D-19): automatic registration from completed builds, forward-only handling transitions (OPEN -> ACKNOWLEDGED -> RESOLVED), comments, rerun requests and the automatic resolvedByRunId link.
    The shipped e-mail BatchControlNotifier (SPEC item 13, D-36).
    Immutable description of one notification (SPEC item 13, D-36), handed to every BatchControlNotifier.
    Hands request events to every BatchControlNotifier on a background thread (D-36).
    The request events a BatchControlNotifier receives (SPEC item 13, D-36).
    D-72 (SPEC item 11): an incident rerun could not recover every parameter value of the failed run (a stashed file, which the build clears when it completes; a core file whose copy under the build directory is gone; a deleted build), so no request was created.
    Daily retention cleanup (SPEC item 12): deletes every month bucket older than the configured retentionMonths — the runs and changes JSONL files, that month's diff patches, and that month's incidents (index + XMLs) — and records each deleted month as ChangeRecord(type=RETENTION) identifying the month as YYYY-MM.
    Keeps the configuration snapshots (the CONFIGURE diff baselines, ARCHITECTURE section 5) in step with the items when change recording becomes active (SPEC item 9).
    Restart durability (SPEC item 4): after every startup, APPROVED requests that never executed are re-submitted exactly once (idempotent via the consumption ticket and the restored-queue/existing-build checks in the policy service).