-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add queue time information #777
Labels
enhancement
New feature or request
Comments
yes, I agree. I think we should use Jenkins API to get all the stage duration time that we have and display them in a logical way. (i.e., in descending order per stage, group by pipeline/platform, with machine name, etc) |
Related: GSoC 2023 proposal to pull some of this information and consider how to best optimize machine usage |
llxia
added a commit
to llxia/aqa-test-tools
that referenced
this issue
Mar 24, 2023
related: adoptium#777 Signed-off-by: Lan Xia <Lan_Xia@ca.ibm.com>
llxia
added a commit
to llxia/aqa-test-tools
that referenced
this issue
Mar 24, 2023
related: adoptium#777 Signed-off-by: Lan Xia <Lan_Xia@ca.ibm.com>
Merged
karianna
pushed a commit
that referenced
this issue
Mar 24, 2023
related: #777 Signed-off-by: Lan Xia <Lan_Xia@ca.ibm.com>
#784 is the initial step. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently pull and parse information from Jenkins pipelines, but do not include the queue time (how long a job waits for a particular machine resource). It will be useful to include this information in what we gather, and then make it available via the TRSS API (just like we do for test execution times) so that we might better forecast resource needs.
The text was updated successfully, but these errors were encountered: