import { type GetBuildByKey } from "https://deno.land/x/jira@v3.0.2/src/agile/models/getBuildByKey.ts";
Data related to a single build*
Properties
The schema version used for this data.
Placeholder to support potential schema changes in the future.
An ID that relates a sequence of builds. Depending on your use case this might be a project ID, pipeline ID, plan key etc. - whatever logical unit you use to group a sequence of builds.
The combination of pipelineId and buildNumber must uniquely identify a build you have provided.
Identifies a build within the sequence of builds identified by the build pipelineId.
Used to identify the 'most recent' build in that sequence of builds.
The combination of pipelineId and buildNumber must uniquely identify a build you have provided.
A number used to apply an order to the updates to the build, as identified by pipelineId and buildNumber, in
the case of out-of-order receipt of update requests.
It must be a monotonically increasing number. For example, epoch time could be one way to generate the
updateSequenceNumber.
Updates for a build that is received with an updateSqeuenceNumber less than or equal to what is currently stored
will be ignored.
An optional description to attach to this build.
This may be anything that makes sense in your system.
The state of a build.
pending- The build is queued, or some manual action is required.in_progress- The build is currently running.successful- The build completed successfully.failed- The build failed.cancelled- The build has been cancelled or stopped.unknown- The build is in an unknown state.
The last-updated timestamp to present to the user as a summary of the state of the build.
The Jira issue keys to associate the build information with.
You are free to associate issue keys in any way you like. However, we recommend that you use the name of the branch the build was executed on, and extract issue keys from that name using a simple regex. This has the advantage that it provides an intuitive association of builds to issue keys.