You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assume ${trssUrl}/api/getTopLevelBuildNames?type=Test will return all three kinds(?) once we have test job run, when we need a better filter (not only contains('-pipeline') ) to get data for different jdk version.
maybe a new section for evaluation (dont think release is needed to count)
The text was updated successfully, but these errors were encountered:
Yes, and I was presuming that the release pipeline (openjdk17-release-pipeline) and evaluation pipeline (openjdk17-evaluation-pipeline) and nightly pipeline will be explicitly named differently, and I would update which pipelines we are monitoring in TRSS**, so we could then query children independently:
Since we introduced the new "release" and "evaluation" pipeline,
the current https://ci.adoptopenjdk.net/view/Tooling/job/nightlyBuildAndTestStats_temurin/ probably need to be updated accordingly.
Assume ${trssUrl}/api/getTopLevelBuildNames?type=Test will return all three kinds(?) once we have test job run, when we need a better filter (not only
contains('-pipeline')
) to get data for different jdk version.maybe a new section for evaluation (dont think release is needed to count)
The text was updated successfully, but these errors were encountered: