| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
|
|
| |
Sigh, JSON, why must you be so generally awful.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
|
|
| |
To get ppc64 tasks run on stg but not prod.
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>
|
|
|
|
| |
These roles need the -fedora subpackage, not just the main lib.
|
|
|
|
| |
I'll wipe the from-source installs manually, seems easiest.
|
| |
|
|
|
|
| |
In check-compose and openqa/dispatcher roles, now it's packaged.
|
|
|
|
|
|
| |
The scheduler binary name changed from 'fedora-openqa-schedule'
to 'fedora-openqa', but I forgot to update the call in this
cronjob. Oops.
|
|
|
|
| |
I split the package, we don't need the CLI, only the lib.
|
|
|
|
| |
goddamnit, adam, why'd you make so many options.
|
|
|
|
| |
gah, section names.
|
| |
|
| |
|
|
|
|
|
| |
We split fedora_openqa and createhdds out into their own repos,
this should adapt to the change (I hope).
|
|
|
|
|
|
|
| |
This is a bit sloppy and infra-specific ATM, but does the job.
I have a PR in for openqa_fedora_tools which changes the report
behaviour a bit, once that lands I'll clean this up somewhat
using variables.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
relvalconsumer is the fedmsg consumer bot that creates Wikitcms
release validation test events. Up till now it's just been
running on one of my personal boxes; we should really move it
to infra. Run it on the openQA servers for now, as there's
nowhere more obviously correct, and I have root access there to
fix problems.
We add new inventory groups because it's *really important*
that there be exactly one (no more, no less) production consumer
at any given time. I don't want to just use the 'openqa' group
for this because it's vaguely possible it could contain more
than one host in future, and we really wouldn't want that to
result in there being two production relvalconsumers running.
|
| |
|
|
|
|
|
| |
We fixed the issue which meant ARM kernel / initrd file names
were colliding, so we don't need this workaround any more.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
...d'oh, one day i'll get this right
|
| |
|
|
|
|
|
|
|
| |
since resultsdb submission was added to the scheduler, we must
disable it here for now (as we don't want to use it yet), and
also update the name of the config directive that controls wiki
result submission.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
...by extending the fedmsg consumer config file. Requires the
latest openqa_fedora_tools to work.
|
|
|
|
|
| |
we need some from updates-testing for now. also, we need
openqa-httpd for the server.
|
|
|
|
| |
we only needed it once.
|
| |
|
| |
|
|
|
|
|
| |
ditch the old systemd consumer service, install the fedmsg
consumer config file, add some fedmsg-hub reload notifications.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
...otherwise you end up scheduling jobs with stale code and
they fail, NOT THAT THAT'S EVER HAPPENED TO ME
|
| |
|
| |
|
| |
|
|
|
|
|
| |
mainly systemd unit changes, clean up the old ones, enable the
new.
|
|
|
|
| |
we moved the openqa scheduler within the git checkout.
|