8d1d150 Handle running update tests on Koji tasks

Authored and Committed by adamwill 5 years ago
    Handle running update tests on Koji tasks
    
    We quite often want to run the update tests on a Koji task (not
    a Bodhi update) for some reason - usually to test a potential
    fix for an issue, or at a maintainer's request to test a change
    before it is merged upstream and officially sent out as an
    update. Up till now I've always hacked up utils.pm on the
    staging server by hand to do this, which is horrible. Together
    with a commit to fedora_openqa, this should allow us to do it in
    a nice, sane way via the CLI. It's mostly just tweaking the
    "updates" repo setup in utils.pm as you'd expect, but there's a
    bit of subtlety to it because of the installer tests that use
    %ADVISORY% as a variable substitution in the disk image name;
    you can't do something like `%ADVISORY or KOJITASK%`, sadly, so
    I had to have almost-redundant variables ADVISORY, KOJITASK and
    ADVISORY_OR_TASK (we could kinda just live with ADVISORY_OR_TASK
    except I didn't want to drop ADVISORY as it's an unnecessary
    change from previous behavior).
    
    Signed-off-by: Adam Williamson <awilliam@redhat.com>
    
        
file modified
+1 -0
file modified
+16 -9
file modified
+12 -12
file modified
+1 -1
file modified
+3 -3
file modified
+1 -1