Interface BuildData

BuildData

Data related to a single build

interface BuildData {
    buildNumber: number;
    description?: string;
    displayName: string;
    issueKeys: string[];
    label?: string;
    lastUpdated: string;
    pipelineId: string;
    references?: ({
        commit?: {
            id: string;
            repositoryUri: string;
        } & {
            [key: string]: unknown;
        };
        ref?: {
            name: string;
            uri: string;
        } & {
            [key: string]: unknown;
        };
    } & {
        [key: string]: unknown;
    })[];
    schemaVersion?: "1.0";
    state:
        | "failed"
        | "pending"
        | "unknown"
        | "in_progress"
        | "successful"
        | "cancelled";
    testInfo?: {
        numberFailed: number;
        numberPassed: number;
        numberSkipped?: number;
        totalNumber: number;
    } & {
        [key: string]: unknown;
    };
    updateSequenceNumber: number;
    url: string;
}

Hierarchy

  • Record<string, unknown>
    • BuildData

Properties

buildNumber description? displayName issueKeys label? lastUpdated pipelineId references? schemaVersion? state testInfo? updateSequenceNumber url

Properties

buildNumber

buildNumber: number

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.

Example

16

Optionaldescription

description?: string

An optional description to attach to this build.

This may be anything that makes sense in your system.

Example

My Project build #16: Failed

displayName

displayName: string

The human-readable name for the build.

Will be shown in the UI.

Example

My Project build #16

issueKeys

issueKeys: string[]

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.

Optionallabel

label?: string

A human-readable string that to provide information about the build.

lastUpdated

lastUpdated: string

The last-updated timestamp to present to the user as a summary of the state of the build.

Example

2018-01-20T23:27:25.000Z

pipelineId

pipelineId: string

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.

Example

my-build-plan

Optionalreferences

references?: ({
    commit?: {
        id: string;
        repositoryUri: string;
    } & {
        [key: string]: unknown;
    };
    ref?: {
        name: string;
        uri: string;
    } & {
        [key: string]: unknown;
    };
} & {
    [key: string]: unknown;
})[]

Optional information that links a build to a commit, branch etc.

OptionalschemaVersion

schemaVersion

The schema version used for this data.

Placeholder to support potential schema changes in the future.

Example

1

state

state:
    | "failed"
    | "pending"
    | "unknown"
    | "in_progress"
    | "successful"
    | "cancelled"

BuildState

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.

Example

failed

OptionaltestInfo

testInfo?: {
    numberFailed: number;
    numberPassed: number;
    numberSkipped?: number;
    totalNumber: number;
} & {
    [key: string]: unknown;
}

TestInfo

Information about tests that were executed during a build.

Type declaration

  • numberFailed: number

    The number of tests that failed during a build.

    Example

    5
  • numberPassed: number

    The number of tests that passed during a build.

    Example

    145
  • OptionalnumberSkipped?: number

    The number of tests that were skipped during a build.

    Example

    0
  • totalNumber: number

    The total number of tests considered during a build.

    Example

    150

updateSequenceNumber

updateSequenceNumber: number

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.

Example

1523494301448

url

url: string

The URL to this build in your system.

Settings

Member Visibility

On This Page

Properties