eG Help

Bitbucket Pipeline is an integrated continuous integration (CI) / continuous delivery (CD) service, built into Bitbucket. One or more Bitbucket Pipelines can be configured to automatically build, test and even deploy your code through different branches without affecting the main Bitbucket repository. The Pipelines execute the operations based on a configuration file committed to the main Bitbucket repository. The Pipelines give you end-to-end visibility from coding to deployment and bring the status of builds on the branches into your repository. In the process, you can also view the status of different branches and commits everywhere in Bitbucket, thus giving you crucial visibility on the status of your builds when you branch and before you merge.

With Bitbucket Pipelines, all teams can determine any failures during code building/testing/deploying operations, fix them as earlier as possible and deliver better software faster. If, for any reason, build operations using the Pipelines on fail or are halted or stopped abruptly, then the code will not be built as expected. This in turn will delay tasks that should be performed after the build operation and code synchronization and reduce reliability. As a result, the continuous delivery of software will become questionable. To avoid such anomalies, administrators can use the BitBuktPipeTest to proactively detect the status of builds executed on branches through Pipelines.

This test continuously monitors the branches of the repositories, and for each branch of each repository, proactively reveals the number of successful builds and the number of builds that failed/stopped/halted and are in pending state. These statistics help administrators to find out how well/badly the build operations are performed on each branch, proactively detect the issues, if any, and take remedial actions immediately.

Outputs of the test : One set of results for each repository in the Bitbucket account being monitored

Measurement	Description	Measurement Unit	Interpretation
totalbuildCount	Indicates the total number of builds that run on this branch.	Number
successCount	Indicates the number of builds that run successfully for this branch.	Number	The detailed diagnosis of this measure reveals the name of author, commit ID, brief message, trigger type, build ID, the time at which the build operation was started and the total time duration taken for build operation in seconds.
failedCount	Indicates the number of builds that failed on this branch.	Number	The detailed diagnosis of this measure reveals the name of author, commit ID, brief message, trigger type, build ID, the time at which the build operation was started and the total time duration taken for build operation in seconds.
pendingCount	Indicates the number of builds that are pending on this branch.	Number	The detailed diagnosis of this measure reveals the name of author, commit ID, brief message, trigger type, build ID, the time at which the build operation was started and the total time duration taken for build operation in seconds.
haltedCount	Indicates the number of builds that are halted on this branch.	Number	The detailed diagnosis of this measure reveals the name of author, commit ID, brief message, trigger type, build ID, the time at which the build operation was started and the total time duration taken for build operation in seconds.
stoppedCount	Indicates the number of builds stopped on this branch.	Number	The detailed diagnosis of this measure reveals the name of author, commit ID, brief message, trigger type, build ID, the time at which the build operation was started and the total time duration taken for build operation in seconds.