Tag candidate composes as 'important'
ClosedPublic

Authored by adamwill on Mar 28 2017, 9:12 PM.

Details

Summary

openQA has a feature letting you mark builds as 'important' by
adding a comment in a specific format to the job group. This has
a couple of implications. Jobs for the build won't be eaten by
the garbage collector (that otherwise deletes most artifacts of
jobs after a certain time). Also, jobs for the build won't be
cancelled if a 'similar' build is scheduled while they're
running. We had a problem today where all the jobs for F26 Alpha
RC4 were cancelled because an F26 nightly landed shortly after
they started, and openQA decided the nightly jobs should
'obsolete' the RC4 jobs. This will preven that happening again.

Test Plan

Run the test suite, and if you have a pet openQA
instance, you can test this quite easily by just scheduling
some jobs for a candidate compose and, while they're running,
scheduling jobs for a nightly of the same release. The result
should be that both sets of jobs are run (none are cancelled).

Diff Detail

Repository
rOPENQA fedora_openqa
Branch
important-candidate (branched from master)
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 1117
Build 1117: arc lint + arc unit
adamwill created this revision.Mar 28 2017, 9:12 PM

Hmm, for some reason, RC4 jobs still got obsoleted by newest nightly when I've tried it. I'm not sure whether tagging works on my instance, because it doesn't show tags next to group name (as shown here) and also when I filter for "tagged", it doesn't show any group. Only thing that worked for me is setting _NOOBSOLETEBUILD=1 as they mention in their documentation. I should debug why tagging doesn't work for me.

yeah, actually I think I saw the same when testing with a manual tag. But I'm 99% sure the format of the tag is correct. It may be that the openQA we're running currently is broken, or just older than this feature? I'll take a look too.

I've fixed the openQA bug in the 4.4-46 package build, just submitted to updates-testing. If you try again with that openQA package, it should work.

jsedlak accepted this revision.Mar 30 2017, 12:50 PM

Code works OK.

This revision is now accepted and ready to land.Mar 30 2017, 12:50 PM
adamwill closed this revision.Mar 30 2017, 1:26 PM