Data pipeline export schema
Users file
Field | Description |
---|---|
user_id | Type: String Description: ID of the user Example: |
instance_url | Type: URL Description: Base URL of the current instance. Example: |
user_name | Type: String Description: User name of the user. Example: |
user_fullname | Type: String Description: Full name of the user. Example: |
user_email | Type: Email Description: Email address of the user. Example: |
Repositories file
Field | Description |
---|---|
| Type: Number Description: Unique identifier for the repository. Example: |
| Type: URL Description: Base URL of the current instance. Example: |
| Type: String Description: URL of the repository. Example: |
| Type: String Description: Name of the repository. Example: |
| Type: String Description: Description of the repository. |
| Type: Number Description: The unique identifier for the hierarchy of forks to which this repository belongs. All repositories have a hierarchy ID, even if they have no forks. Example: |
| Type: String Description: Repository from which this repository was forked, if any. Example: |
| Type: Number Description: Unique identifier for the project. Example: |
| Type: String Description: Key of the project this repo is contained in. Example: |
| Type: String Description: Name of the project this repo is contained in. Example: |
| Type: String Description: Whether the project the repository is contained in is normal or personal. Example: |
| Type: Boolean Description: ‘Allow forks’ is selected in the repository settings. Example: |
| Type: Boolean Description: Repository is forked from another repository. Example: |
| Type: Boolean Description: Whether ‘Public access’ is enabled in the repository settings. Example: |
Commits file
Field | Description |
---|---|
| Type: String Description: Unique identifier of the commit. Example: |
| Type: URL Description: Base URL of the current instance. Example: |
| Type: URL Description: URL of the commit. Example: |
| Type: String Description: Commit message included with the commit. |
| Type: Number Description: Unique identifier for the repository. Example: |
| Type: String Description: Email address of the author of the committed code. If the author is not a Bitbucket user, this email will not map to a user in the users table. Example: |
| Type: Date Description: Date and time the commit was made. Example: |
| Type: String Description: Email address of the user who committed the code. If the committer is not a Bitbucket user, this email will not map to a user in the users table. Example: |
| Type: Date Description: Date and time the commit was last modified. Example: |
Pull requests file
Field | Description |
---|---|
| Type: String Description: Unique identifier of the pull request. It is a combination to_repository_id & scoped_id. Example: |
| Type: Number Description: Identifier for the pull request. This ID is only unique within each repository. Example: |
| Type: URL Description: Base URL of the current instance. Example: |
| Type: String Description: URL of the pull request. Example: |
| Type: String Description: Title of the pull request. Example: TEST-123 fix broken tests |
| Type: String Description: Description included with the pull request, limited to XXX characters. |
| Type: Number Description: Unique identifier of the person who created the pull request. Example: |
| Type: Date Description: Date the pull request was created. Example: |
| Type: Date Description: Date the pull request was updated. Example: |
| Type: Date Description: Date the pull request was closed. Example: |
| Type: String Description: The name of the source branch. Example: Improve-tests |
| Type: String Description: The commit hash for the earliest commit in this pull request. Example: |
| Type: Number Description: Unique identifier for the source repository. Example: |
| Type: String Description: The name of the destination branch. Example: |
| Type: String Description: The commit hash for the latest commit in this pull request. Example: |
| Type: Number Description: Unique identifier for the destination repository. Example: |
| Type: Number Description: Version number represents the number of times the pull request has been updated. Example: |
| Type: String Description: Current status of the pull request. Can be MERGED, DECLINED, or OPEN. Example: |
| Type: Number Description: Number of participants on the pull request. |
| Type: Number Description: Number of reviewers on the pull request. |
| Type: Number Description: Number of approvals on the pull request. |
| Type: Number Description: Number of comments on the pull request. |
| Type: Number Description: Total number of tasks on the pull request. |
| Type: Number Description: Number of tasks resolved on the pull request. |
| Type: Number Description: Time between pull request creation and merge, in milliseconds. Example: |
Build status file (optional)
plugin.data.pipeline.bitbucket.export.build.statuses
system property to true
to enable it.Field | Description |
---|---|
| Type: String Description: Commit hash for the commit. Example: |
| Type: Number Description: Unique identifier of the repository. Example: |
| Type: String Description: Key set in your CI tool. Can be used as a unique identifier when combined with repository ID and commit ID. Example: |
| Type: String Description: URL of the build in your CI tool. Example: |
| Type: String Description: Name of the build. Example: |
| Type: Number Description: The identifier for the specific run that resulted in this build status. May be empty. Example: |
| Type: String Description: Description of the specific run that resulted in this build status. Example: |
| Type: Number Description: Duration of the build, in milliseconds. Example: 230400 |
| Type: Date Description: Date the build was created. Example: |
| Type: Date Description: Date the build was updated. Example: |
| Type: String Description: State of the build. Can include SUCCESSFUL / FAILED / INPROGRESS Example: |
| Type: String Description: Key of the parent build for this plan. Can be empty. Example: |
| Type: String Description: The branch or tag that this build is associated with. Can be empty. |
| Type: Number Description: The number of successful tests in this build. |
| Type: Number Description: The number of failed tests in this build. |
| Type: Number Description: The number of skipped tests in this build. |