Previous commit didn't work as the directory doesn't exist.
Also, I think we need the file in two places, one for root
(for if an admin runs something wikitcms-ish manually while
logged in as root) and one for fedmsg (for the usual case
when the wiki is updated by fedmsg consumers). So do that.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Unattended wiki interaction with the new openidc auth method
requires a special token file which @puiterwijk created and
put in the private store for us. Have the appropriate roles
install it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Like with openqa/server, sometimes we have the fedora_openqa
checkout in some kind of testing state on staging. We want to
skip the git checkout step when this is the case. This is just
copied across from the server role.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There are no fedmsg notifications for the live respin composes,
so we just try scheduling them every hour; when we've already
tested the current compose this will not create any new jobs,
and when a new compose shows up, this will test it.
We currently can't tell openQA to download the ARM kernel and
initramfs with a filename unique to the build being tested, so
they just get downloaded as `vmlinuz` and `initrd.img`, which
means that when the next compose is tested, we won't download
them again, we'll just use the existing copies (which are no
longer the right ones). Because of this our current 'F25' and
'Rawhide' ARM tests are actually still using some F24 kernel
image. Until the openQA bug which prevents us giving the files
unique names is resolved, here's a hacky workaround: a script
which wipes the files every hour if no openQA jobs are pending.
necessary updates for openqa roles have gone stable for now, so
disable updates-testing usage (keep the plays around commented,
though, since we'll likely need them again in future). Also, a
bit more attempted support for non-infra use: make the monkey
patching of the repo URLs in the test templates only happen if
deployment_type is defined, actually respect the openqa_consumer
var (don't enable the job scheduling consumer unless it's truey)
and only enable any wiki reporting consumer if deployment_type
is defined.
with openQA jobs being scheduled and wiki results reported
(well, when we get that working again) by fedmsg-hub consumers,
we have to let the fedmsg user read these files.
Both 'server' and 'dispatcher' roles need to check out openqa_
fedora_tools, but only 'dispatcher' needs to install it. To
avoid having to register a variable in 'server' too and have
the install task check if either variable |changed, just have
two separate checkouts, so the dispatcher checkout will always
have 'changed' when appropriate.
This adds openQA server, worker and dispatcher roles, and
applies them to the appropriate hosts. A few secret vars are
required. See trac #4958 for discussion.
