QA (public) » openQA Project (public) » openQA Tests (public)

I enabled "Throttle builds" in http://jenkins.qa.suse.de/job/gnome_next-openqa/configure with max. 6 builds/day while allowing user triggered builds to skip the rate limit

Previously the "URLTrigger" monitored http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME_Next* but this is now served by MirrorCache which has no "last-modified" timestamp but also the content always changes as the generated HTML page shows a "csrf-token" changing on each call. I found that by calling

diff <(curl -sS "http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME_Next*") <(curl -sS "http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME_Next*")

which yields:

<       <meta name="csrf-token" content="3a72819665c9adb750ad4d5e8054961c5b1c3efc" />
---
>       <meta name="csrf-token" content="0b17cbf73c393a1baa4daee989158038caeafc7c" />

I switched the URLTrigger to inspect the URL content of http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/GNOME_Next.x86_64.iso.sha256 which is small enough to not be a problem to be recurringly downloaded. Let's see if this works.

And I created https://github.com/openSUSE/MirrorCache/issues/349

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

The current build history in http://jenkins.qa.suse.de/job/gnome_next-openqa/ looks like we trigger as many as the build throttle allows. But checking for example the latest finished build http://jenkins.qa.suse.de/job/gnome_next-openqa/7830/ from Feb 3, 2023, 12:53:00Z, comparing to http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/ the latest modified is 1320Z so for sure there had been changes today. Let's monitor for longer.

It seems the process is working fine. We seem to have sometimes multiple builds per day of GNOME Next but maybe we don't need that. So I will just keep the build throttle in place.