All Classes and Interfaces
Class
Description
An immutable record of a human's answer to a
Question.Versioned JSON REST API rooted at
/interactive-input/api/v1/ (§6.3, §8.6).The
askInteractive pipeline step (§6.1): a durable, human-answered input step that surfaces
in the notification bell and rich modal.Durable, restart-safe execution for
AskInteractiveStep.Keeps interactive-input notifications in step with the build lifecycle: when a build is deleted its
questions and reviews must stop appearing in the global notification centre and stop counting towards
the sidebar badge (previously they lingered because nothing cleaned them up on deletion).
Purges questions and marks reviews build-deleted the moment a build is removed.
One-shot startup reconciliation for builds deleted before this cleanup was in place.
Resolves a short, human-readable "who/what started this build" label for a
Run, used to
attribute interactive-input questions in the notification surfaces ("started by <user>").A single selectable option offered to the human, optionally carrying a
why rationale
that explains, in plain language, when this option is the right one.Descriptor so
Choice is a first-class Describable for the step's repeatable
choice form (B17).Metadata for one persisted version of a
ReviewDocument's content.An
HttpResponse that streams a byte payload as a browser file download (Interactive View
download feature, item #1).Notify-only email channel.
Splits and sanitises a comma/semicolon-separated recipient list.
Detects whether the current viewer has opted into Jenkins' experimental "new build/job page"
layouts, so the plugin can render its per-build/per-job content as native cards there instead of
inside core's hardcoded "Legacy" card (see
jenkins/run/OverviewTab/index.jelly and
jenkins/job/OverviewTab/index.jelly).Per-capability functional feature flags (§6.4), shown under Manage Jenkins →
System.
Maps a file name to a
ReviewDocument render format and a Prism language hint.Immutable pairing of a render format and a Prism language id.
Opt-in bridge that surfaces built-in
input steps in the notification bell (§3.1 S5, §8.7).Appearance-facing configuration for the plugin's notification surfaces (§6.4).
Global, JCasC-compatible configuration for the plugin (§6.4, §8.8).
Per-project notification centre (§per-project surfaces).
Attaches
InteractiveInputJobAction to every job when the per-project centre is enabled.Per-pipeline outbound notification channels, shown in Configure as an opt-in checkbox
("Interactive Input notifications") that reveals an add-channel list.
Per-build notification + audit surface (§per-project surfaces).
Attaches
InteractiveInputRunAction to builds that have interactive-input questions.Per-pipeline opt-in for the run-page "needs attention" indicator (review item B5), shown in
Configure as its own checkbox alongside the separate "Interactive Input notifications"
property.
Native "Interactive Input" attention card for the experimental run overview — the experimental-layout
counterpart of
InteractiveInputRunAction's summary.jelly (B5 attention row), which is
suppressed when the new build page is on.Attaches the tab to builds of jobs that opted into the run-page attention indicator (same gate as
the classic row).
Per-build "Interactive Output" surface published by the
interactiveOutput step.Per-job "Interactive Output" trend surface.
A single per-report chart model exposed to
index.jelly / output.js.Attaches
InteractiveOutputJobAction to every job when the per-project centre is enabled.Native "Interactive Output" card for the experimental run overview.
Attaches the tab to any build carrying a visible
InteractiveOutputBuildAction.The
interactiveOutput pipeline step: publish per-build statistics (cost, carbon footprint,
resource usage, …) as KPI cards + a table on the build page, and feed a per-job trend chart.Synchronous execution for
InteractiveOutputStep: builds a MetricReport from the
step's metrics, attaches it to the build's InteractiveOutputBuildAction (creating the action
on first use), persists the build and — when notify is set — logs an anchored console link to
the output page.Per-job "Interactive View" surface.
Attaches
InteractiveViewJobAction to every job when per-project surfaces are enabled.Per-build "Interactive View" surface.
Attaches
InteractiveViewRunAction to builds that have review documents.Native "Interactive View" card for the experimental run overview — the review counterpart of
InteractiveOutputRunTab.Attaches the tab to any build that has review documents (same gate as
InteractiveViewRunAction).A report group prepared for
widget.jelly: the report name, its reviews, and whether the
report-name heading adds information — so the template needs no list-size or element logic.The
interactiveView pipeline step: snapshot a generated file into the plugin's durable store
and publish a Confluence-style review page where humans can comment (generally or inline, per source
line), edit a durable review copy (with version history) and record an
approve / reject / acknowledge / request-changes decision.Durable, restart-safe execution for
InteractiveViewStep.An
HttpResponse that writes a JSON body with an explicit HTTP status code.Safe markdown-to-HTML rendering for the modal's context panel and free-text preview (§7.5).
A single statistic published by the
interactiveOutput step: a labelled value with an
optional unit and an optional stable key.A named group of
Metrics published by one interactiveOutput call (e.g.Injects the notification-centre data mount and shared client into every Jenkins page (§6.2.1, §8.4).
Header-button
RootAction for the notification centre.A notify-only outbound delivery channel (email, Teams webhook, Slack webhook, or a future
extension).
Queues notify-only outbound delivery off the pipeline thread.
QuestionStoreListener that only queues; must not block QuestionStore#submit.ViewStoreListener that only queues; must not block ViewStore#submit.Immutable snapshot handed to
NotificationChannel.send(io.jenkins.plugins.interactiveinput.notify.NotificationEvent).Absolute Jenkins URLs for outbound notifications.
A console hyperlink that opens a specific interactive-input question's dialog in place on
the page that shows the link (B6).
Notification-bell polling settings (§6.4).
A single human-in-the-loop question raised by the
askInteractive step (or mirrored from a
built-in input step by the bridge).Lifecycle state of a human-in-the-loop
Question.In-memory registry of human-in-the-loop
Questions with XStream persistence to
$JENKINS_HOME/interactive-input/questions.xml (§8.1, §8.2).Callback invoked once when a question reaches a terminal state.
Extension point fired by
QuestionStore on every question state transition.A single Confluence-style comment on a
ReviewDocument.A durable, reviewable snapshot of a file published by the
interactiveView pipeline step.Lifecycle state of an
interactiveView review document.Serves an
interactiveView HTML snapshot for display inside a sandboxed frame, so a
reviewer can look at a generated report (a Robot Framework log.html, an Allure/pytest report,
…) instead of only its escaped source.Default SLA settings (§6.4).
Notify-only Slack incoming webhook.
Periodic task that expires overdue questions, compacts terminal ones (§8.3, §8.9) and reconciles
the opt-in input-step bridge (§8.7).
Notify-only Microsoft Teams incoming webhook.
In-memory registry of
ReviewDocuments published by the interactiveView step, with
XStream persistence of the metadata to $JENKINS_HOME/interactive-input/views.xml and the
content versions stored as separate files under $JENKINS_HOME/interactive-input/views/<id>/.Callback invoked once when a blocking review reaches a decided (or expired) state.
Extension point fired by
ViewStore when a review document is published.Secret-text credential lookup and form fill for Slack/Teams webhook URLs.
POSTs a JSON body to an incoming-webhook URL.