QA » openQA Project

From the sync and trigger side, on a new build: If there are no builds within the last >24h, call sync with _NOOBSOLETEBUILD. That's it. That should do no harm if there are >builds within the last 24h that are completely finished anyway.

I think it should be "If there are no 'completed' builds within 24 hours (ie no builds with skipped jobs)"

This will also then resolve the 'lots of half tested builds' problem by ensuring we do at least one full test of at least one build every 24 hours

where are we with this? Is one build finishing?

#13560 was about only syncing complete architectures. In the same change I also prepared for no obsoletion but rbrown and ast prefer it to stay as in before for now: https://gitlab.suse.de/openqa/scripts/merge_requests/59#note_38622
It is just a simple switch but it is off now. the ticket is in state "new", it's not started. Try to convince them, implement it yourself or wait :-)

updated MR as the original approach could not work. It would call "deprioritize-or-cancel" every time when "openqa-iso-sync-sles" would be called and there is no build in progress or a dirty repository is present. I changed the approach to call the script from within rsync.pl just before it triggers an ISO.

so build 0271 came in, solution works in principle but the deprioritizing on all jobs running on a product is done per arch and medium so too much depriorization in one step and also jobs are cancelled then, even running ones

testing the state after initial medium got triggered:

In [11]: jobs = requests.get('https://openqa.suse.de/api/v1/jobs?state=running&state=scheduled&latest=1&flavor=Server-DVD').json()
In [12]: {j['id']: j['settings']['BUILD'] for j in jobs['jobs']}
Out[12]: 
{806799: '0267',
 806801: '0267',
…
 806954: '0267',
 807143: '0271',
…

so suggestions to improve:

• match more specifically on the exact jobs of one medium/flavor/arch to deprioritize and cancel
• do not cancel running jobs at all, only scheduled

https://github.com/os-autoinst/openQA/pull/1255 merged

https://gitlab.suse.de/openqa/scripts/merge_requests/69 merged

osd is already deployed with that new version.

So far three builds have been triggered for SLE since that change and jobs of old builds are still running. So far the old version of openqa/scripts has been used with "obsolete=1". Comparing the currently scheduled virtualization jobs I can see no depriorization, e.g. sle-12-SP3-Server-DVD-x86_64-Build0278-gi-guest_sles11sp4-on-host_sles12sp3-kvm@64bit-ipmi has prio 50 as well as sle-12-SP3-Server-DVD-x86_64-Build0274-gi-guest_sles11sp4-on-host_sles12sp3-kvm@64bit-ipmi as expected.

Also debug output is available now, e.g.:

[Thu Mar 16 15:17:43 2017] [7918:debug] Triggering new iso with build '0126', obsolete: 1, deprioritize: 0        
[Thu Mar 16 16:17:24 2017] [16888:debug] Triggering new iso with build '0127', obsolete: 1, deprioritize: 0       

Checked out master of openqa/scripts on osd and re-enabled cron-job so now waiting for new build which is triggered by the new version of trigger scripts.