Builds the model of a component from a kind of job: a chain of jobs with downstream dependencies, or a Pipeline job. The first source that {@linkplain #supports supports} a job owns it, in extension order.
Implementations:
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Finds the projects a project triggers. Jenkins core knows about build triggers and anything that declares itself in the dependency graph; other plugins contribute their own relations through this extension point.
Implementations:
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Finds the runs a run started, as the {@code build} step of Pipeline does. The plugin that provides such a step records them on the run that started them; an integration reads that record when the plugin is installed.
Implementations:
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Knows which projects are triggered by a person rather than automatically, and how to perform such a trigger. The Build Pipeline plugin's manual trigger is the one implementation that ships with this plugin.
Implementations:
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Restarts a finished Pipeline run from one of its top-level stages, for the flavours of Pipeline that support it. Declarative Pipeline does; the integration with it activates when that plugin is installed.
Implementations:
Delivery Pipeline Plugin: se.
Adds facts about a build to its task: test results, static analysis results and promotions. Test results come from the JUnit plugin; the others are contributed by optional integrations when their plugins are installed.
For a Pipeline run the tasks are stages, so test results are asked for per flow block: the block of the stage, nested stage or parallel branch the task shows.</p>
Implementations:
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.
Delivery Pipeline Plugin: se.