PipePlan class

Lays out the stages and the steps of the build and publish commands

Both commands have the same layout:

  1. A stage before the platforms: the preparations of the command, then pre_platform_run. When any of them fails, no platform runs
  2. A stage with a step per platform, in BPConfig.platformOrder. The platforms are independent, so a failed platform does not stop the others. A platform with hooks or extra steps is a group of pre_command, the build or the upload, the extra steps, post_command.on_success, and post_command.finally
  3. A stage after the platforms: post_platform_run.on_success, which runs only when nothing has failed, and post_platform_run.finally, which runs in any case

Constructors

PipePlan()

Properties

hashCode → int
The hash code for this object.
no setterinherited
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited

Static Methods

build(BPConfig config) → List<PipeStage>
The stages of build_pipe:build
publish(BPConfig config) → List<PipeStage>
The stages of build_pipe:publish

Constants

platformNames → const Map<TargetPlatform, String>
The user-facing names of the platforms