Package io.jenkins.plugins.batchcontrol.policy
package io.jenkins.plugins.batchcontrol.policy
-
ClassDescriptionActivation approval (SPEC item 6a, D-39): whether a run-controlled job may run unattended, and the single entry point for every
ActivationRequeststate transition and everyActivationStatewrite.Approver eligibility rules (SPEC items 2 and 3), shared byRunRequestServiceandGrantRequestService.e2e-03 DEF-25 (SPEC item 6 and section 6 usability): the rebuild plugin's Rebuild and Rebuild Last entries are not offered on builds of a job whose manual runs need an approved run request (RunRequestService.requiresApprovalToRun(hudson.model.Job<?, ?>)), because the queue gate refuses every such rebuild.The reason texts of requests that end without a decision (e2e-04 FD-05, D-54).The single entry point for everyGrantRequeststate transition (SPEC items 3 and 8).D-72: disposal of the temporary files that typed parameter values keep until a build takes them over, for values that will never reach the queue: a run request that ended without a run (REJECTED, CANCELLED, EXPIRED, INVALIDATED before it was queued), a submission that was refused before a request was stored, a person's own build submission that the queue gate refused, or rerun values that could not be completed.D-72, D-74 (2): the size cap on a run request submission.D-72b (4), security-37 S-37-01: a run request refused because what it would keep (its file contents and the stored text of its other values,RequestBodyLimit.keptSize(java.util.List<? extends hudson.model.ParameterValue>, java.util.Map<java.lang.String, java.lang.Long>)) is over the capRequestBodyLimit.maxRequestBodyBytes().The single entry point for everyRunRequeststate transition (SPEC items 3, 5, 7; D-20/D-21/D-22/D-23).