Skip to main content

Version 5.7.3


  • Implemented functionality to find Next and Previous Error Logs. Buttons “Show”, “Next” and “Previous” error logs minimize user’s efforts of scrolling across all the available logs.
  • Improved lazy loading: the number of pre-loaded logs is 300 which helps to get a better understanding of preconditions to a certain error. What is more, now it’s possible to load 300 more logs or load all the current step at once.
  • “Stack trace” in log messages now loads all the Error Logs. Besides, with the help of “Jump to” button on the Error Log it’s possible to switch to this Error Log displayed in the “All Logs” view.

Small and nice updates:

#3109 Launch and test item description limits have been increased to 2048. Improved description view on all the “Launches” pages means that now even more useful links, artifacts, OKRs, etc can be stored in the description.


We have refactored logs double-entry saving to Elasticsearch by changing index type: now logs are saved in indexes per project instead of indexes per launch. It helps us to save the performance of Elasticsearch considering other operations and the data which we have processed via Elastic. More details can be found via the link.

Technical updates:

  • Updated RabbitMQ to 3.10.7.
  • Environment variable added for Service Jobs to configure http/https usage (added to values.yaml for RabbitMQ as well).
  • Added the logics of logs deletion (by jobs): when the logs are deleted by jobs from PostgreSQL, they are also deleted from ElasticSearch.

CVE addressed: