QA (public) » openQA Project (public)

Motivation¶

There has been a reset of the JeOS build counter for SLE15SP3 which brings some challanges to the openQA webui because sorting by build number is not feasible anymore. There is an option to sort by the newest job that is contained in a build but that has flaws as well.

Eg at https://openqa.suse.de/admin/job_templates/131 I can select in the jobgroup settings the following sorting options: Sort by build value (as a version) and Sort by time job most recently created. It would produce more stable results if there was a 3rd option Sort by time job least recently created. That would not mess with the build order if there is a rebuild of a job in an older build triggered.

So I want to sort the builds in the jobgroup by the oldest job that this testsuite contains.
This will make the sorting order much more resilient against manual rebuilds of single jobs in older builds.

Note that this might still be relevant because also on other products the build number might reset or the numbering scheme might change (so sorting by time in a more stable way would be preferable).

Acceptance criteria¶

• AC1: There is a sort option for builds on job group level that sorts builds in descending order (newest builds on top). It looks at the least recent jobs within a build to do this. (In contrast to the existing option that looks at the most recent job within a build.)

Suggestions¶

• Look for examples where this feature will be useful
• This likely requires database and UI changes
  • A database migration to convert the column we're currently storing the sort order from boolean to integer (to allow more than 2 options). (e.g. alter table ... alter build_version_sort type int USING build_version_sort::integer)
  • A 3rd radio button within the UI.
  • Adjust %search_opts in compute_build_results depending on the setting. Likely changing max => 'id' to min => 'id' in case of the new option would work.
• Ask @AdamWill (or whoever initially created the existing time-base sorting) whether it would be ok to switch it to consider the least recent job (and just change the existing option instead of adding a new 3rd one)