Bitbucket Repositories Test

A repository is the most basic element of Bitbucket and shareable with teammates. You can create a new repository on your personal account or any organization where you have sufficient permissions. The repository contains all of the project's files and stores each file's revision history. You can also discuss and manage your project's work within the repository. Repositories can be either public or private and can have multiple collaborators. Public repositories are visible to everyone, on the other hand, a private repository can be viewed and contributed only by the owner and collaborators. As the repositories are the basic units and shared among multiple users, it is important for the account owners to be up-to-date about the size and workload of the repositories in their account. The Bitbucket Repositories test helps the account owners in this regard.

This test auto-discovers the repositories in the target Bitbucket account and for each repository, reports whether/not the repository is private and the count of commit operations performed on each repository. In addition, the detailed diagnosis provided by the test reveals the record of what changes were made when and by who. This helps the account owners to keep track of the commit operations and to know if any of the changes were done by unauthorized users. This test also reveals the workload on each repository in terms of issues and pull requests. This way, the unsolved issues are brought to the immediate attention of the account owners, so that they can investigate the reason for the same and fix them. In the process, this test also sheds light on the size of each repository. Using this revelation, the account owners can instantly know whether the repository size is within the acceptable limit or has increased abnormally. If the repositories are detected to be in large size, the account owners can initiate remedial measures to prevent slowness during fetching files from the repositories.

Target of the test : Bitbucket

Agent deploying the test : An internal agent

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

Configurable parameters for the test
Parameters Description

Test period

This indicates how often should the test be executed.


The host for which this test is to be configured.


The port at which the host listens to.

Username, Password and Confirm Password

Specify the user name and password assigned to the Bitbucket account to be monitored in the Username and Password text boxes.

Then, confirm the password by retyping it in the Confirm Password text box.

Excluded Repositories

Here, you can provide a comma-separated list of repository names that you do not want to monitor. For instance, to exclude repositories with names that contain 'ver1' and 'ver2' from monitoring, your specification should be: *ver1*,*ver2*

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is private repository?

Indicates whether/not this repository is private repository.


The values that this measure can report and the states they indicate have been listed in the table below:

Measure Value Numeric Value
Yes 1
No 0


By default, this measure can report the Measure values mentioned above while indicating the current state of the resources. However, the graph of this measure is indicated using the numeric equivalents.

The detailed diagnosis of this measure gives the resource group name, resource name, resource class, provider, resource type, and node name.

Last updated

Indicates the time elapsed since the last update.




Indicates the number of issue types created in this repository.




Indicates the number of forks of this repository.


A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

The detailed diagnosis of this measure reveals name of the user and fork repository.


Indicates the number of watches of this repository.


Watches allow you to receive notification on certain actions performed in the repository, for example, when a new code pushed to the repository or when a pull request is merged. Watches can be set on the repository or on branches of your interest.

The detailed diagnosis of this measure reveals the profile name and user name of the watchers.


Indicates the number of files that are uploaded to this repository.


The detailed diagnosis of this measure reveals the name and size of the file that was uploaded to each repository, the name of use by whom the file was uploaded, etc.

Repository size

Indicates the size of this repository.


Compare the value of this measure to know which repository is bigger in size.

The value reported by this measure helps a repository administrator to know whether the size of the repository is within an acceptable limit or has increased abnormally. If the size of the repository has increased abnormally, administrator should consider removing the large files from the repository to keep the repository smaller. The smaller repositories ensure that the Bitbucket is fast and downloads are quick for users.

Source files

Indicates the number of source files in this repository.


The detailed diagnosis of this measure reveals the name and size (MB) of source file, when the last commit was done, and brief description.


Indicates the number of times that the commit operation is performed in this repository.


Commit operation is performed when a user wants to push new files or changes to the existing files in his/her repository to the central base repository.

Total branches

Indicates the total number of branches created from this repository.


Branches are created in order to add files and make updates to existing code without affecting code quality and safety of the main code base. When you need to do changes in the main code base, you can do it by creating a new branch and make required changes in the branch without disturbing existing features of the main code base. Then, you can merge the changes to the main code base using a pull request.

Total pull requests

Indicates the total number of pull requests created for this repository.


Pull requests provide you with a method for requesting code reviews from your colleagues and checking build status based on your most recent commit.

Open pull requests

Indicates the number of pull requests that are still open in this repository.



Merged pull requests

Indicates the number of pull requests that are merged to this repository.



Declined pull requests

Indicates the number of pull requests that are declined in this repository.



Release branches

Indicates the number of branches created for release tasks from this repository.


The release branches are used for release task and long-term maintenance versions. They branch from, and merge back into, the development branch. Merging into an older release branch can be configured to automatically merge to newer release branches, as well as the development branch.

Hotfix branches

Indicates the number of branches created from this repository for fixing a production branch without interrupting changes in the development branch.



Feature branches

Indicates the number of branches created from this repository for specific feature work or improvements.



Bugfix branches

Indicates the number of bugfix branches created from this repository.


Typically, the bugfix branches are created fixing the release branches.

Other branches

Indicates the number of other types of branches created from this repository.




Indicates the number of tags created in this repository.


Tags are references that point to specific points in Git history. Tagging is generally used to capture a point in history that is used for a marked version release (i.e. v1. 0.1). A tag is like a branch that doesn’t change. Unlike branches, tags, after being created, have no further history of commits.