QA » openQA Project

Setting due date based on mean cycle time of SUSE QE Tools

We discussed this today, and we have quite different use cases, and the ACs don't really reflect that and only talk about "finished" builds.

In the github worflow of distri-opensuse we select the last published build:

curl -s https://openqa.opensuse.org/group_overview/1.json
 | jq -r '([ .build_results[] | select(.tag.description=="published") | select(.version=="Tumbleweed") | .build ] | sort | reverse)[]'

In our openQA-in-OpenQA tests we want the latest build by sort order, but don't care about published or finished and we only want a job and not the build itself:

resp=$(openqa-cli api --host $openqa_url jobs version=Tumbleweed scope=relevant arch='$arch' flavor=NET test='minimalx' latest=1)
job_id=$(echo "$resp" | jq -r '.jobs | max_by(.settings.BUILD) .id')

Looking for the published tag involves quite some work, so I would basically run pretty much the same code as in the group_overview, and maybe make the tag configurable.

Note that the group_overview is currently fetching all comments for a group in order to attach any found tags to the build list.
Maybe that's also the best approach for now, (because otherwise I would incrementally go over the latest builds and try to find a "published" tag for each of them until I find one). I guess the new route wouldn't be very performance critical for now.

I edited AC1

Draft: https://github.com/os-autoinst/openQA/pull/5433 Add /job_groups/id/build_results API route
Setting to Workable until thursday

https://github.com/os-autoinst/openQA/pull/5433 merged and working on o3:

% openqa-cli api --o3 job_groups/1/build_results time_limit_days=20 show_tags=1 limit_builds=10 only_tagged=1 | jq -r '[.build_results[] | select(.tag.description=="published")  | select(.version=="Tumbleweed") | .build ][]'
20240206
20240205
20240204
20240202
20240201
20240131
20240130
20240129
20240128
20240126

Actually I think I can make PRs for using it as well

Both PRs merged