Configuration of BitBuktIssueTest

A user with a valid account on the Bitbucket cloud can create bug reports, feature requests and project management tasks by simply creating issues in the Bitbucket repositories. When you add a repository to Bitbucket Cloud, you also get an issue tracker. This is the place where the issues are stored to track the status of your project's feature requests, bug reports and other project management tasks. By analyzing the history of issues provided by the issue tracker, the user can instantly know the tasks that were performed frequently, the count of open/closed/resolved issues, the list of invalid/duplicate issues, etc. To help the users in this regard, this test monitors the repositories in the target account, and for each repository, reports the number of different issues in the issue tracker over the time.

The default parameters associated with this test are:

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

• In the HOST text box, specify the HOST for which this test is to be configured.

• The port at which the host listens to is specified in the PORT text box.

• 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*

• By default, SHOW CLOSED ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Closed issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

• By default, SHOW RESOLVED ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Resolved issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

• By default, SHOW WONTFIX ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Wontfix issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

• By default, SHOW ONHOLD ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Onhold issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

• By default, SHOW INVALID ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Invalid issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

• By default, SHOW DUPLICATE ISSUES DD flag is set to Yes, indicating that by default, the test generates detailed measures for Duplicate issues measure. If you do not want the test to generate and store detailed measures for closed issues, set this flag to No.

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

• To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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 bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.