This section describes the CloudBees Analytics data model. It comprises several interrelated schemas that are externalized as report object types.
Data model overview
For CloudBees Analytics comprised of CloudBees CD/RO data, the following data model applies:
The data in each type is sourced as described in the below table. Select an object type for complete details about its structure.
For CloudBees Analytics comprised of CloudBees CI-only data:
Report type | Object name | Description |
---|---|---|
build |
For events related CloudBees CI builds starting and finishing. It is used on the Workload Insights dashboard. |
|
controller_event |
For events related to CloudBees CI controllers starting and for the configuration on a controller being updated. It is used on the Workload Insights dashboard. |
|
ci_license |
For events related to current CloudBees CI licenses. Used by the License usage report. |
|
ci_plugin |
For events related to plugins being installed, uninstalled, or otherwise modified on CloudBees CI controllers. This data is used on the Plugin Usage dashboard. |
|
ci_plugin_usage |
For events related to plugins being used in various ways in CloudBees CI. It is used on the Plugin Usage dashboard. |
|
ci_queue_event |
For events related to activity in the build queue in CloudBees CI, such as new jobs entering the queue, queued jobs starting, or queued jobs being cancelled. It is used on the Workload Insights dashboard. |
|
ci_user_login |
For events related to CloudBees CI user logins. This data is used by the License usage report. |
If CloudBees CD/RO is installed, these additional report types are available:
Report type | Object name | Description |
---|---|---|
EC-Jenkins plugin |
Data derived directly from the Build plugin with contributions from the BuildCommit and Quality plugins. |
|
EC-Jenkins plugin |
Data derived directly from the plugin. |
|
ECSCM-Git plugin |
Data derived from |
|
EC-JIRA plugin |
Data derived directly from the plugin. |
|
CloudBees CD/RO |
Data derived from directly from CloudBees CD/RO. |
|
EC-JIRA plugin |
Data derived directly from the plugin with contributions from release and project data. |
|
EC-FeatureFlags plugin |
Data derived directly from the plugin. |
|
EC-ServiceNow plugin |
Data derived directly from the plugin. |
|
CloudBees CD/RO |
Data derived from directly from CloudBees CD/RO. |
|
CloudBees CD/RO |
Data derived from directly from CloudBees CD/RO, with contributions from Deployment. |
|
EC-ALM plugin |
Data derived directly from the plugin. |
|
CloudBees CD/RO |
Feature, Defect, Incident, PipelineRun, Deployment, Quality, and Build report object types contribute to data in this object |
Report object type reference for CloudBees CD/RO-only data
These report types are available when the data is sourced from CloudBees CD/RO.
Build
-
Object type: Build
-
Report object name: build
-
Description: Build data from Jenkins or CloudBees CD/RO.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Base Drilldown URL |
|
Base URL used to construct the full URL for drilling down from a widget into an external build system such as Jenkins. For example, |
|
Build Number |
|
Unique build number or identifier assigned to the build by the build system. |
|
Build Status |
|
Current status of the build: |
|
Duration |
|
Duration of the build in milliseconds. |
|
End Time |
|
End date and time for the build. The format is ISO 8601 in UTC time. For example, |
|
Launched By |
|
User or process that launched the build. |
|
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through EC-Jenkins. |
|
Plugin Name |
|
Name of the plugin if the data was populated through a plugin such as EC-Jenkins. For example, |
|
Build System Project Name |
|
Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the CloudBees CD/RO project name for polling builds, or the build project name in TFS. |
|
Release Name |
|
Name of the CloudBees CI release to which the build belongs. |
|
Release Project Name |
|
Name of the project containing the release to which the build belongs. |
|
Release URI |
|
Partial URL that can be used along with You can drill down only into the builds of a specific project in Jenkins. |
|
Build System Type |
|
Name of the continuous integration system. For example, |
|
Build URL |
|
URL for the build record. For example, |
|
Start Time |
|
Starting date and time for the build. The format is ISO 8601 in UTC time. For example, |
|
Tags |
|
Tags or labels associated with the build. |
|
Timestamp |
|
Date and time that the build completed. The system uses this field to determine the time-based index for storing the build record by year. For example, builds that completed in 2017 are stored in the index The format is ISO 8601 in UTC time. For example, |
|
Job Name |
STRING |
Name of the job. For CloudBees CI builds, this is set using the name of the job started by CloudBees CD/RO to run the build. It is not used for Jenkins builds. |
Build commit
-
Object type: Build Commit
-
Report object name: build_commit
-
Description: Source code changesets included in builds done by CloudBees CD/RO or Jenkins continuous integration system.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
buildUrl |
Build URL |
|
URL for the build record. For example, |
buildNumber |
Build Number |
|
Unique build number or identifier assigned to the build by the build system. |
startTime |
Start Time |
|
Start date and time for the build. The format is ISO 8601 in UTC time. For example, |
endTime |
End Time |
|
End date and time for the build. The format is ISO 8601 in UTC time. For example, |
buildStatus |
Build Status |
|
Current status of the build: |
projectName |
Build System Project Name |
|
Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the project name for CloudBees CI builds, or the build project name in TFS. |
tags |
Tags |
|
Tags or labels associated with the build. |
buildSource |
Build System Type |
|
Name of the continuous integration system. For example, |
commitDate |
Commit Date |
|
Date when the changeset was committed or checked into the source control system. |
commitId |
Commit ID |
|
Unique identifier for the changeset in the source control management system. For example, SHA number in Git or changelist number in Perforce. |
commitUrl |
Commit URL |
|
URL to the changeset in the SCM repository. |
jobName |
Job Name |
|
Name of the job. For CloudBees CI builds, this is set using the name of the job started by CloudBees CD/RO to run the build. Not used for Jenkins builds. |
scmRepoBranch |
SCM Repository Branch |
|
Repository branch: Specific to Git or Git-based SCMs. For example, |
scmSource |
SCM Type |
|
Name of the source control management system. For example, |
scmUrl |
SCM Server URL |
|
URL to the SCM repository or the SCM server name. For example, |
Code commit
-
Object type: Code Commit
-
Report object name: code_commit
-
Description: Code commit or changeset data from Git or GitHub source code management systems.
Attribute | Display Name | Type | Description |
---|---|---|---|
pluginConfiguration |
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through a plugin such as ECSCM-Git. |
pluginName |
Plugin Name |
|
Name of the plugin if the data was populated through a plugin. For example, ECSCM-Git. |
source |
SCM Type |
|
Name of the source control management system. For example, |
sourceUrl |
Commit URL |
|
URL to the changeset in the SCM repository. |
baseDrilldownUrl |
BaseDrilldown Url |
|
Base URL used to construct the full URL for drilling down from a widget into an external source control management system such as Git. For example, |
commitDate |
Commit Date |
|
Date when the changeset was committed or checked into the source control system. |
scmUrl |
SCM Server URL |
|
URL to the SCM repository or the SCM server name. For example, |
scmRepoBranch |
SCM Repository Branch |
|
Repository branch. This is specific to Git or Git-based SCMs. For example, |
commitId |
Commit ID |
|
Unique identifier for the changeset in the source control management system. For example, the SHA number in Git or the changelist number in Perforce. |
commitAuthor |
Commit Author |
|
Changeset author name |
commitAuthorId |
Commit Author ID |
|
Unique identifier for the changeset author in the source control management system. For example, |
commitMessage |
Commit Message |
|
Commit message provided with the commit or changeset. |
codeLinesAdded |
Code Line Added |
|
Number of code lines added in the commit or changeset. |
codeLinesUpdated |
Code lines Updated |
|
Number of code lines updated in the commit or changeset. |
codeLinesRemoved |
Code Lines Removed |
|
Number of code lines deleted in the commit or changeset. |
filesAdded |
Files Added |
|
Number of files added in the commit or changeset. |
filesUpdated |
File Updated |
|
Number of files updated in the commit or changeset. |
filesRemoved |
Filed Removed |
|
Number of files removed in the commit or changeset. |
Defect
-
Object type: Defect
-
Report object name: defect
-
Description: Defects logged in the Atlassian JIRA defect tracking system.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
baseDrilldownUrl |
Base Drilldown Url |
|
Base URL used to construct the full URL for drilling down from a widget into a defect-tracking system such as Atlassian JIRA. For example, |
createdOn |
Created On |
|
Date and time that the defect was created. The format is ISO 8601 in UTC time. For example, |
defectName |
Defect Name |
|
Name of the defect. |
key |
Unique Defect ID |
|
Unique identifier for the defect in the defect tracking system. |
modifiedOn |
Modified On |
|
Date and time that the defect was last modified. The format is ISO 8601 in UTC time. For example, |
pluginConfiguration |
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through EC-JIRA. |
pluginName |
Plugin Name |
|
Name of the plugin if the data was populated through EC-JIRA. For example, |
releaseName |
Release Name |
|
Name of the release containing the defect. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the defect. |
releaseUri |
Release URI |
|
Partial URL that can be used along with For example, for JIRA, if |
resolution |
Resolution |
|
Current resolution of the defect. The possible values depend on the defect tracking system. |
resolvedOn |
Resolved On |
|
Date and time that the defect was resolved. The format is ISO 8601 in UTC time. For example, |
source |
Source |
|
Name of the defect tracking system. For example, |
sourceUrl |
Source Url |
|
URL for the defect record. For example, |
status |
Status |
|
Current status of the defect: |
timestamp |
Timestamp |
|
Date and time when the defect record was last updated. The system uses this field to determine the time-based index for storing the defect records by year. For example, defects updated in 2017 are stored in the index The format is ISO 8601 in UTC time. For example, |
type |
Type |
|
Defect type. The possible values depend on the defect tracking system. The possible value for JIRA is |
Deployment
-
Object type: Deployment
-
Report object name: deployment
-
Description: Data from CloudBees CD/RO application or microservice deployments.
Attribute | Display Name | Type | Description |
---|---|---|---|
applicationId |
Application ID |
|
Unique ID of the application that was deployed. |
applicationName |
Application Name |
|
Name of the application. |
approvedBy |
Approved By |
|
User who approved the manual step. |
clusterName |
Cluster Name |
|
Name of the cluster to which the service was deployed. |
comment |
Comment |
|
Comment provided when the user completed the manual step. |
deploymentOutcome |
Deployment Outcome |
|
Outcome of the deployment: |
elapsedTime |
Elapsed Time |
|
Time taken by the deployment to complete (in milliseconds). |
environmentId |
Environment ID |
|
Unique ID of the environment to which the application or service was deployed. |
environmentName |
Environment Name |
|
Name of the environment. |
environmentProjectName |
Environment Project Name |
|
Name of the environment project. |
flowRuntimeId |
Runtime ID |
|
ID of the pipeline run that started or triggered the deployment. |
flowRuntimeName |
Runtime Name |
|
Name of the pipeline run that started deployment. |
flowRuntimeStateName |
Runtime State Name |
|
Name of the stage or task that started the deployment. |
groupName |
Group Name |
|
Name of the group containing the task. |
jobAbortStatus |
Job Abort Status |
|
Abort status if the job was aborted: |
jobAbortedBy |
Job Aborted By |
|
User who aborted the job. |
jobFinish |
Job Finish |
|
Job completion time. |
jobId |
Job ID |
|
Unique job ID. |
jobName |
Job Name |
|
Name of the job. |
jobOutcome |
Job Outcome |
|
Outcome of the job: |
jobStart |
Job Start |
|
Job start time |
jobStatus |
Job Status |
|
Status of the job: |
jobStepAbortStatus |
Job Step Abort Status |
|
Abort status of the job step: |
jobStepAbortedBy |
Job Step Aborted By |
|
User or project that aborted the job step. |
jobStepName |
Job Step Name |
|
Name of the job step. |
jobStepOutcome |
Job Step Outcome |
|
Outcome of the job step: |
jobStepStatus |
Job Step Status |
|
Status of the job step: |
jobStepType |
Job Step Type |
|
Type of the job step. |
jobType |
Job Type |
|
Type of the job: |
launchedByUser |
Launched By User |
|
User who launched the job. |
manual |
Manual |
|
Boolean flag to indicate if a step is manual. |
parentTaskId |
Parent Task ID |
|
ID of parent task. |
parentTaskName |
Parent Task Name |
|
Name of the parent task. |
parentTaskType |
Parent Task Type |
|
Task type of the parent task. |
pipelineId |
Pipeline ID |
|
ID of the pipeline containing the task that launched the job. |
pipelineName |
Pipeline Name |
|
Name of the pipeline containing the task that launched the job. |
pipelineRunOutcome |
Pipeline Run Outcome |
|
Outcome of the pipeline run: |
plannedEndTime |
Planned End Time |
|
Planned end date of the task that triggered the deployment. |
plannedStartTime |
Planned Start Time |
|
Planned start date of the task that triggered the deployment. |
pluginDisplayName |
Plugin Display Name |
|
Display name of the plugin. |
pluginKey |
Plugin Key |
|
Key of the plugin. |
processId |
Process ID |
|
ID of the process that launched the job. |
processName |
Process Name |
|
Name of the process that launched the job. |
processStepName |
Process Step Name |
|
Name of the process step in the process. |
projectId |
Project ID |
|
ID of the project. |
projectName |
Project Name |
|
Name of the project. |
releaseId |
Release ID |
|
ID of the release to which the pipeline runs belongs. |
releaseName |
Release Name |
|
Name of the release to which the pipeline run belongs. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release. |
reportEventType |
Report Event Type |
|
Type of report event:
|
retries |
Retries |
|
Number of times to retry a step upon an error. |
retryType |
Retry Type |
|
Type of retry: |
serviceId |
Service ID |
|
ID of the service associated with the job. |
serviceName |
Service Name |
|
Name of the service associated with the job. |
stageName |
Stage Name |
|
Name of the stage containing the task that launched the job. |
taskName |
Task Name |
|
Name of the task that launched the job. |
taskStatus |
Task Status |
|
Status of the task. |
taskType |
Task Type |
|
Type of task:
|
tierMapName |
Tier Map Name |
|
Name of the tier map. |
waitForPlannedStart |
Wait For Planned Start |
|
Boolean flag that represents whether a task should wait for a planned start date before running. |
Feature
-
Object type: Feature
-
Report object name: feature
-
Description: Features or stories tracked in the Atlassian JIRA project management tool .
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
baseDrilldownUrl |
Base Drilldown Url |
|
Base URL used to construct the full URL for drilling down from a widget into a system such as JIRA. For example, |
createdOn |
Created On |
|
Date and time that the feature was created. The format is ISO 8601 in UTC time. For example, |
featureName |
Feature Name |
|
Name of the feature. |
featuretype |
Feature Type |
|
Type of the feature : |
key |
Unique Feature ID |
|
Unique identifier for the feature in the project management tool. |
modifiedOn |
Modified On |
|
Date and time that the feature was last modified. The format is ISO 8601 in UTC time. For example, |
pluginConfiguration |
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through EC-JIRA. |
pluginName |
Plugin Name |
|
Name of the plugin if the data was populated through EC-JIRA. For example, |
releaseName |
Release Name |
|
Name of the release containing the feature. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the feature. |
releaseUri |
Release URI |
|
Partial URL that can be used along with |
resolution |
Resolution |
|
Current resolution of the feature. Possible values include: |
resolvedOn |
Resolved On |
|
Date and time that the feature was resolved. The format is ISO 8601 in UTC time. For example, |
source |
Source |
|
Name of the project management tool. For example, |
sourceUrl |
Source Url |
|
URL for the feature record. For example, |
status |
Status |
|
Current status of the feature: |
storyPoints |
Story Points |
|
Number of story points assigned to the feature. This can be any integer. |
tags |
Tags |
|
Tags or labels associated with the feature. |
timestamp |
Timestamp |
|
Date and time that the feature record was last updated. The system uses this field to determine the time-based index for storing the feature records by year. For example, features updated in 2017 are stored in the index The format is ISO 8601 in UTC time. For example, |
Feature flags
-
Object type: Feature Flag Report
-
Object name: feature_flag
-
Description: Data from Feature Flag Management
Attribute | Display Name | Type | Description |
---|---|---|---|
Release information |
|||
|
Release Name |
STRING |
Name of the CloudBees CD/RO release collected data relates to. |
|
Release Project Name |
STRING |
Name of the CloudBees CD/RO release project collected data relates to. |
Context information |
|||
|
Application ID |
STRING |
The ID of the application from which to retrieve flags. |
|
Application Name |
STRING |
Name of the application. |
|
Environment ID |
STRING |
Unique ID of the environment to which the application was deployed. |
|
Environment Name |
STRING |
Name of the environment. |
Feature flag information |
|||
|
Name |
STRING |
The name of the feature flag, |
|
Description |
STRING |
The user-provided description of the feature flag. |
|
Created |
DATETIME |
|
|
Updated |
DATETIME |
|
|
Enabled |
BOOLEAN |
If |
|
Labels |
STRING |
|
|
Platforms |
STRING |
|
|
BOOLEAN |
If |
|
|
Status |
STRING |
enumerationValues = |
Event generation time |
|||
|
Time Stamp |
DATETIME |
|
Usage information |
|||
|
Number of Usages |
NUMBER |
The number of feature flag usage for the last polling interval date range (by default 6 hours) or the summarized number of usages from the beginning. |
Incident
-
Object type: Incident
-
Report object name: incident
-
Description: Incidents logged and managed in the ServiceNow ITSM system for post-production deployed releases.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
baseDrilldownUrl |
Base Drilldown Url |
|
Base URL used to construct the full URL for drilling down from a widget into a system such as ServiceNow. For example, |
category |
Category |
|
Category containing the incident. The possible values depend on the ITSM system. |
configurationItem |
Configuration Item |
|
Configuration item name for the incident in the ITSM system. |
createdOn |
Created On |
|
Date and time that the incident was created. The format is ISO 8601 in UTC time. For example, |
incidentId |
Unique Incident ID |
|
Unique ID of the incident. |
modifiedOn |
Modified On |
|
Date and time that the incident was last modified. The format is ISO 8601 in UTC time. For example, |
pluginConfiguration |
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through EC-ServiceNow. |
pluginName |
Plugin Name |
|
Name of the plugin if the data was populated through EC-ServiceNow. For example, |
priority |
Priority |
|
Incident priority. The possible values depend on the ITSM system. |
releaseName |
Release Name |
|
Name of the release for which the incident occurred. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release for which the incident occurred. |
releaseUri |
Release URI |
|
Partial URL that can be used along with |
reportedBy |
Reported By |
|
Username of the reporter of the incident. |
resolvedOn |
Resolved On |
|
Date and time that the incident was resolved. The format is ISO 8601 in UTC time. For example, |
source |
Source |
|
Name of the ITSM system. For example, |
sourceUrl |
Source URL |
|
URL for the incident record in the source system. For example, |
status |
Status |
|
Current status of the incident. Possible values include |
subCategory |
Sob Category |
|
Subcategory containing the incident. The possible values depend on the ITSM system. |
timestamp |
Timestamp |
|
Date and time when the incident was last updated. The system uses this field to determine the time-based index for storing the incident records by year. For example, updated in 2017 are stored in the index The format is ISO 8601 in UTC time. For example, |
Job
-
Object type: CloudBees CD/RO Job
-
Report object name: job
-
Description: Data from CloudBees CD/RO jobs (the output associated with invoking a CloudBees CD/RO procedure or process).
Attribute | Display Name | Type | Description |
---|---|---|---|
applicationId |
Application ID |
|
Unique ID of the application process for which the job was run. |
applicationName |
Application Name |
|
Name of the application. |
elapsedTime |
Elapsed Time |
|
Time taken by the job to complete (in milliseconds). |
environmentId |
Environment ID |
|
Unique ID of the environment to which the application or service was deployed. |
environmentName |
Environment Name |
|
Name of the environment. |
environmentProjectName |
Environment Project Name |
|
Name of the environment project. |
flowRuntimeId |
Pipeline Run ID |
|
ID of the pipeline run that started or triggered the job. |
jobFinish |
End Time |
|
Job completion time. |
jobID |
Job ID |
STRING |
Unique job ID. |
jobName |
Job Name |
|
Name of the job. |
jobStart |
Start Time |
|
Job start time. |
combinedStatus |
Job Result |
|
Set using |
launchedByUser |
Launched By User |
|
User who launched the job. |
pipelineId |
Pipeline ID |
|
ID of the pipeline containing the task that launched the job. |
projectName |
Project Name |
|
Name of the project. |
releaseId |
Release ID |
|
ID of the release to which the pipeline runs belongs. |
releaseName |
Release Name |
|
Name of the release to which the pipeline run belongs. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release. |
serviceId |
Service ID |
|
ID of the service associated with the job. |
serviceName |
Service Name |
|
Name of the service associated with the job. |
tags |
Tags |
|
Tags associated with the job. |
Pipeline run
-
Object type: Pipeline Run
-
Report object name: pipelinerun
-
Description: Data from pipeline runs in CloudBees CD/RO such as pipeline run outcome and runtime start and end times.
Attribute | Display Name | Type | Description |
---|---|---|---|
action |
Manual task/step action |
|
Action the user took to complete the manual task or step: |
applicationName |
Application Name |
|
Name of the application. |
applicationProjectName |
Application Project Name |
|
Name of the project containing the application. |
approvedBy |
Approved By |
|
Name of the user who approved the stage or gate task. |
approvers |
Approvers |
|
List of approvers for the stage or gate task. |
elapsedTime |
Elapsed Time |
|
Time taken by the pipeline run to complete (in milliseconds). |
evidence |
Evidence |
|
Evidence that the task was run. |
flowRuntimeAbortStatus |
Pipeline Run Abort Status |
|
Abort status of the pipeline run if it was aborted: |
flowRuntimeAbortedBy |
Pipeline Run Aborted By |
|
User who aborted the pipeline run. |
flowRuntimeCompleted |
Pipeline Run Completed |
|
Boolean flag to indicate if the pipeline run is completed. |
flowRuntimeFinish |
Pipeline Run Finish Time |
|
Time when the pipeline run was completed. |
flowRuntimeId |
Pipeline Run ID |
|
ID of the pipeline run. |
flowRuntimeName |
Runtime Name |
|
Name of the pipeline run. |
flowRuntimeStart |
Pipeline Run Start Time |
|
Time when the pipeline run started. |
flowRuntimeStateAbortStatus |
Task/Stage Run abort status |
|
Abort status of a stage, task, or gate associated with the pipeline run: |
flowRuntimeStateAbortedBy |
Task/Stage Run aborted by |
|
User who aborted the stage, task, or gate in the pipeline run. |
flowRuntimeStateFinish |
Task/Stage Run finish time |
|
Time when the stage, task, or gate finished execution in the pipeline run. |
flowRuntimeStateId |
Task/Stage Run ID |
|
ID of the runtime object associated with the stage, task, or gate in the pipeline run. |
flowRuntimeStateName |
Runtime State Name |
|
Name of the runtime object associated with the stage, task, or gate in the pipeline run. |
flowRuntimeStateOutcome |
Runtime State Outcome |
|
Outcome of execution of the runtime object associated with the stage, task, or gate in the pipeline run: |
flowRuntimeStateStart |
Task/Stage Run start time |
|
Time when the stage, task, or gate started execution in the pipeline run. |
gateType |
Gate Type |
|
Type of gate: |
groupName |
Group Name |
|
Name of the group task. |
manual |
Manual |
|
Boolean flag to indicate if it is a manual or an approval task. |
parentTaskId |
Parent Task ID |
|
Id of parent task. |
parentTaskName |
Parent Task Name |
|
Name of the parent task (either a deployer task or a group task). |
parentTaskType |
Parent Task Type |
|
Type of the parent task. |
pipelineId |
Pipeline ID |
|
Unique ID of the pipeline. |
pipelineName |
Pipeline Name |
|
Name of the pipeline. |
pipelineRunOutcome |
Pipeline Run Outcome |
|
Outcome of the pipeline run: |
projectId |
Project ID |
|
ID of the project containing the pipeline run. |
projectName |
Project Name |
|
Name of the project containing the pipeline run. |
releaseId |
Release ID |
|
ID of the release associated with the pipeline run. |
releaseName |
Release Name |
|
Name of the release associated with the pipeline run. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release associated with the pipeline run. |
reportEventType |
Report Event Type |
|
Type of the report event:
|
retries |
Retries |
|
Number of times to retry the step after an error. |
retryType |
Retry Type |
|
Type of retry: |
serviceName |
Service Name |
|
ID of the service. |
serviceProjectName |
Stage Project Name |
|
Name of the project that contains the service. |
stageName |
Stage name |
|
Name of the stage that contains the task. |
tags |
Tags |
|
Tags associated with a pipeline or release run. |
taskName |
Task Name |
|
Name of the task. |
taskStatus |
Task Status |
|
Status of the task. |
taskType |
Task Type |
|
Type of task:
|
plannedEndTime |
Task/Stage planned end time |
|
Planned end date of the task. |
plannedStartTime |
Task/Stage planned start time |
|
Planned start date of the task. |
waitForPlannedStart |
Wait For Planned Start |
|
Boolean flag indicating if a stage or task should wait for a planned start time. |
Quality
-
Object type: Quality
-
Report object name: quality
-
Description: Test results obtained from Application Life System Management (HP ALM) systems or the Jenkins continuous integration system.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
baseDrilldownUrl |
Base Drilldown Url |
|
Base URL used to construct the full URL for drilling down from a widget into a system such as HP ALM or Jenkins. For example, |
buildNumber |
Build Number |
|
Number assigned to the build by the build system. This field is applicable only for test results obtained from a build. This can be any integer. |
category |
Category |
|
Category for the tests. For example, |
duration |
Duration |
|
Duration of the tests in milliseconds. |
failedTests |
Number of Failed Tests |
|
Number of tests that failed. This can be any integer. |
manual |
Manual |
|
Whether the tests were run manually. |
pluginConfiguration |
Plugin Configuration |
|
Name of the plugin configuration if the data was populated through EC-Jenkins or EC-ALM. |
pluginName |
Plugin Name |
|
Name of the plugin if the data was populated through EC-Jenkins or EC-ALM. For example, |
releaseName |
Release Name |
|
Name of the release to which the test result belongs. |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release to which the test result belongs. |
releaseUri |
Release URI |
|
Partial URL that can be used along with You can drill down only into the builds of a specific job in Jenkins. With HP ALM, you can drill down only into the project in HP ALM. |
runId |
Test Run ID |
|
Unique ID of the test run. |
skippedTests |
Number of Skipped Tests |
|
Number of skipped tests. This can be any integer. |
source |
Source |
|
Name of the source system from which the test results were obtained. For example, |
sourceUrl |
Source Url |
|
URL for the test result record in the source system. For example, |
status |
Status |
|
Status of the test runs. The possible values depend on the source system. |
successfulTests |
Number of Successful Tests |
|
Number of tests that have succeeded. This can be any integer. |
timestamp |
Timestamp |
|
Date and time that the tests completed. The system uses this field to determine the time-based index for storing the test quality record by year. For example, tests that completed in 2018 are stored in the index |
Release
-
Object type: Release
-
Report object name: release
-
Description: Data from application or microservice releases in CloudBees CD/RO, such as planned and actual start and end times.
Attribute | Display Name | Type | Description |
---|---|---|---|
actualEndTime |
Actual End Time |
|
Actual end time for the release. |
actualStartTime |
Actual Start Time |
|
Actual start time for the release. |
plannedEndTime |
Planned End Time |
|
Planned end date for the release. |
plannedStartTime |
Planned Start Time |
|
Planned start date for the release. |
releaseId |
Release ID |
|
Unique ID for the release. |
releaseDuration |
Release Duration |
|
Duration of the release in milliseconds. |
releaseName |
Release Name |
|
Name of the release |
releaseProjectName |
Release Project Name |
|
Name of the project containing the release. |
tags |
Tags |
|
Tags associated with the release. |
Report object type reference for CloudBees CI-only data
You use attributes for CloudBees Analytics report objects when creating custom reports and dashboards. The following tables list the attributes for the CloudBees Analytics report object types.
CloudBees Software Delivery Automation Build
-
Object type: build
-
Report object name: Build
-
Description: Build data from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Build Number |
STRING |
Unique build number or identifier assigned to the build by CloudBees CI. |
|
Build Status |
STRING |
Current status of the build: |
|
Detail name |
STRING |
The full display name from the CloudBees CI job. |
|
CI Job Name |
STRING |
The full job name from the CloudBees CI job. |
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller Name |
STRING |
CloudBees CI controller name. |
|
Duration |
|
Duration of the build in milliseconds. |
|
End Time |
|
End date and time for the build. The format is ISO 8601 in UTC time. For example, |
|
QueueTime |
|
Time the job entered the queue. The format is ISO 8601 in UTC time. For example, |
|
Build System Type |
STRING |
Name of the continuous integration system. For example, |
|
Start Time |
|
Starting date and time for the build. The format is ISO 8601 in UTC time. For example, |
Controller events
-
Object type: controller_event
-
Report object name: Controller events
-
Description: Controller event data from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
Event |
STRING |
enumerationValues = |
|
DATETIME |
||
|
DATETIME |
||
|
DATETIME |
CloudBees CI license data
-
Object type: CloudBees CI license data
-
Report object name: ci_license
-
Description: License data from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
License version |
STRING |
Version of the CloudBees CI license. |
|
Customer name |
STRING |
Name of the CloudBees CI user of the license. |
|
Organization unit |
STRING |
Organizational unit. |
|
STRING |
The display name of the edition. |
|
|
BOOLEAN |
Presence of |
|
|
STRING |
A pack of plugins (used only on old licenses). |
|
|
Start time |
DATETIME |
The license is valid after this date. |
|
Expiry time |
DATETIME |
The license is valid before this date. |
|
License source |
Enumeration values: |
|
|
Available seats |
NUMBER |
Number of seats in the license. |
CloudBees CI plugin
-
Object type: CloudBees CI plugin
-
Report object name: ci_plugin
-
Description: Plugin information from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
STRING |
||
|
STRING |
||
|
Plugin ID |
String |
The CloudBees CI plugin ID. |
|
Plugin name |
STRING |
Name of the CloudBees CI plugin. |
|
Plugin version |
STRING |
Version of the CloudBees CI plugin. |
|
Timestamp |
Date |
Date and time of plugin event. |
|
Is supported by CloudBees |
BOOLEAN |
Whether the CloudBees CI plugin is supported in the CloudBees Assurance Program (CAP). |
|
Is proprietary |
BOOLEAN |
Whether the CloudBees CI plugin is a CloudBees proprietary plugin. |
|
Event type |
enumerationValues: |
Lifecycle type of the plugin. |
CloudBees CI plugin usage
-
Object type: CloudBees CI Plugin Usage
-
Report object name: ci_plugin_usage
-
Description: Plugin usage data from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
STRING |
Description of the report. |
|
|
Plugin ID |
STRING |
The CloudBees CI plugin ID. |
|
Plugin name |
STRING |
The name of the CloudBees CI plugin. |
|
Plugin version |
STRING |
Version of the CloudBees CI plugin. |
|
Timestamp |
DATETIME |
Plugin event date and time. |
|
Is supported by CloudBees |
BOOLEAN |
Whether CloudBees CI plugin is supported in the CloudBees Assurance Program. |
|
Is proprietary |
BOOLEAN |
Whether CloudBees CI plugin is proprietary. |
|
Job full name |
STRING |
Full name of the CloudBees CI job. |
|
Build URL |
STRING |
Relative build URL to the Jenkins root URL. |
|
Job URL |
STRING |
Relative job URL to the Jenkins root URL. |
|
Item full name |
STRING |
Full name of the configuration item. |
|
Dependent plugin ID |
STRING |
CloudBees CI dependent plugin ID. |
|
Dependent plugin name |
STRING |
Name of the dependent plugin. |
|
Dependent version |
STRING |
Version of the CloudBees CI dependent plugin. |
|
Usage type |
enumerationValues: |
Usage type of the plugin. |
CloudBees CI queue event
-
Object type: CloudBees CI Queue Event
-
Report object name: ci_queue_event
-
Description: CloudBees CI queue event data.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
Event type |
STRING |
enumerationValues = |
|
Queue Item ID |
STRING |
|
|
Queue Size |
NUMBER |
The size of the queue. |
|
DATETIME |
Date and time of the event. |
|
|
Queued at |
DATETIME |
The time that the job or task was added to the queue. |
|
Start time |
DATETIME |
The time that a queued job or task left the queue and started executing. |
|
Cancelled time |
DATETIME |
The time that a queued job or task was cancelled. |
CloudBees CI user login data
-
Object type: CloudBees CI user login data
-
Report object name: ci_user_login
-
Description: User login data from CloudBees CI.
IPv6 addresses are only supported for Kubernetes platforms. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .
|
Attribute | Display Name | Type | Description |
---|---|---|---|
|
ID |
STRING |
|
|
Controller URL |
STRING |
CloudBees CI controller or the CloudBees CI operations center URL. |
|
Controller name |
STRING |
CloudBees CI controller name. |
|
STRING |
Name of the user. |
|
|
STRING |
Email of the user, |
|
|
Timestamp |
DATETIME |
Timestamp for this user’s login session. |
|
Category |
Enumeration values: |
|
|
Enumeration values: |
STRING |
|
|
Source |
Enumeration values: |
|
|
Enumeration values: |