Default Parameters for BitBuktReposTest

This test auto-discovers the repositories in the target Bitbucket account and for each repository, reports whether/not the repository is private and 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.

This page depicts the default parameters that need to be configured for the BitBuktReposTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the user name and password assigned to the Bitbucket account to be monitored in the USERNAME and PASSWORD text boxes.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• Provide a comma-separated list of repository names that you do not want to monitor in the EXCLUDED REPOSITORIES text box. For instance, to exclude repositories with names that contain ‘ver1’ and ‘ver2’ from monitoring, your specification should be: *ver1*,*ver2*

• The 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.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.