Hi, folks! Just wanted to fill everyone in on openQA upgrade plans. I have upgraded the staging server and worker boxes to Fedora 24. prod is still on Fedora 23 for now.
I have built current git os-autoinst and openqa, plus latest upstream perl-Mojolicious-Plugin-AssetPack (which is needed for new openqa), for Rawhide. More-or-less identical builds for F24 are available in this COPR: https://copr.fedorainfracloud.org/coprs/adamwill/openQA-stg/ My pet openqa - https://openqa.happyassassin.net - is currently running those packages, as a first step in testing if they work OK. So far it seems to be alright. This week I'm planning - if Emmanuel Seyman from the perl SIG is OK with it - to send out the same three builds to updates-testing for F24, and update staging to the new openqa and os-autoinst. If that all appears to go OK, I'll move on to updating prod to F24 and the new openqa/os-autoinst. The changes to AssetPack are a bit unfortunate; basically, openQA is now pretty tied to a design where the web assets (CSS and JavaScript) that it uses have to be pulled from remote servers and cached at some point, which is awkward for packaging. On the plus side, the cached assets no longer change every time openQA or AssetPack changes, but only when openQA does. After thinking it through I've gone for an approach similar to SUSE's, by adding a script to the package git repo which generates the asset cache and stuffs it into a tarball, which is then included as a Source1 for the package, so the final packages just include a pre-generated copy of the asset cache. Whoever's doing the packaging (so, uh, me...) has to run the script to re-generate the asset cache any time we bump to a new upstream openQA checkout or release. Please do check out the new packages and the deployment on happyassassin and yell if you see any problems. Note that some tests are failing on happyassassin because I haven't built all the hard disk images (that box is limited in disk space) and for some reason tests that try to upload the disk image after they finish tend to fail on that deployment (I've never managed to work out why). The most obvious change is that the web UI has been rather revamped (and now uses the distro-neutral icon that the Fedora design team came up with, yay!) but there's other stuff as well, you can dig through the openqa and os-autoinst git changelogs to see what... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ qa-devel mailing list qa-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/qa-devel@lists.fedoraproject.org
