Request for a new machine for temurin-compliance for private TRSS instance
Summary
This is a machine request for a modest x64 Linux machine needed to https://github.com/temurin-compliance/temurin-compliance/issues/395, we would like to run a private TRSS server (in a container) to monitor the https://ci.eclipse.org/temurin-compliance Jenkins server. Instructions for setting up a TRSS instance are at: https://github.com/adoptium/aqa-test-tools/tree/master/TestResultSummaryService#docker-compose
Steps to reproduce
https://github.com/adoptium/aqa-test-tools/tree/master/TestResultSummaryService#docker-compose
What is the current bug behavior?
Not a bug report.
What is the expected correct behavior?
n/a
Relevant logs and/or screenshots
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")
Running a private TRSS instance will be extremely helpful in triaging our releases. The TRSS tool helps see historical results, do comparisons, filtering, sorting, searches, and trends.