Skip to content

v6.0.0
Compare
Choose a tag to compare
@elrayle elrayle released this 13 Feb 18:47
v6.0.0
d6be545
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Actions Required to Upgrade

Update to qa_server v6.0.0

bundle update qa_server

Changes

The major change in this release is improved caching of data for the monitor status page and the running of monitoring tests in background. This prevents the page from reporting errors due to timeouts.

There are a few other refactors which impact public method APIs, thus causing the major release. Functionally, everything remains the same. The changes impact the Admin UI only and have no impact on the search and fetch APIs.

New Configuration Options

There is one new configuration which is optional and has a default value.

The datatable under Authority Connection History on the Monitor Status page previously calculated from all available data. A new configuration was added to allow sites to control the time period that is used to calculate data for the history graph and datatable.

  • config.historical_datatable_default_time_period = :year

It is recommended that you copy the new configurations to keep your local config file in sync with the configurations.

Copy only the new configs...

FROM: lib/generators/qa_server/templates/config/initializers/qa_server.rb
TO: config/initializers/qa_server.rb

Change Log

  • refactor generation of performance graphs to minimize db access and calculations
  • shorten race_condition times for caching
  • rename jobs_logger to be monitor_logger
  • run monitoring tests in background
  • move methods from QaServer to services
  • use presenter to get failure data
  • move controller validation code to module include
  • limit historical data to configurable time period
  • move time_period where clause construction to service
Assets 2
Loading