[MGNLCE-16] Add a memory monitor to the integration tests Created: 06/Jan/16  Updated: 15/Nov/21  Resolved: 15/Nov/21

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: estimate-with-uncertainty
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Improve QA setup
Story Points: 8

 Description   

Our build sometimes fail to log a user because the build consumes too much memory.
This doesn't mean that the latest changes caused the issue since there could be already more integrated changes which increased the memory bit by bit.
We should at least be able to check the memory consumption of previous builds if the last build fails.



 Comments   
Comment by Maxime Michel [ 15/Nov/21 ]

Although it would be nice to assess whether any given commit has memory performance on the instance, Jenkins performance is no longer an issue for IT tests.

Generated at Mon Feb 12 00:05:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.