That is awesome, thank you for doing all of this, Adam! Hoping we get our first validation event today, will let you know if I see any issues. Paul ----- Original Message ----- > Hey folks! > > I just wanted to post a heads-up that I have finally finished tweaking > python-wikitcms and the wiki templates themselves to enable the > creation of release validation events for Fedora-IoT composes. I > deployed this to production today. > > What this should mean is that the next time a "Fedora 33" IoT compose > completes, we'll get a validation event created for it and an > announcement mail will be sent to test-announce@ , just like for > regular Fedora composes. > > IoT validation events will have only one matrix page, called "General". > I based the template on the one pwhalen has been using to manually > create events. This is Paul's page: > > https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Test_Template > > and this is the 'official' Wikitcms matrix template page: > > https://fedoraproject.org/wiki/Template:General_IoT_test_matrix > > There will still be a Summary page, even though it doesn't make much > sense with only one matrix page, just because it'd be a chunk of work > to disable the use of Summary pages in this situation. I might do that > later. > > IoT composes are slightly "odd" in that they're always built with the > 'production' type which is meant for release candidate composes, even > though they're functionally nightlies they don't use the 'nightly' > type. Because of this, I've had to special-case the handling of IoT > composes throughout the code, and for wikitcms purposes we will > essentially treat all IoT composes as if they were nightlies. The > 'milestone' for IoT validation events will always be "RC" (at least as > long as the composes are still done this way), and the announcement > emails will always be the "nightly"-style emails, not the "candidate"- > style emails. > > Page names, category names etc. follow the same general pattern as > those for 'normal' validation events, but with "Fedora-IoT" or "IoT" in > them, so the actual matrix page for an event will be something like > https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_33_RC_20200513.0_General > . > There will also be a 'current' redirect page: > https://fedoraproject.org/wiki/Test_Results:Current_IoT_General_Test > categories will exist with similar name modifications, so there'll be a > https://fedoraproject.org/wiki/Category:Fedora-IoT_33_Nightly_Test_Results > and so on. > > I'll also set up testcase_stats for this stream once we have a > validation page, and I'll hook up openQA result reporting so openQA > tests that run on IoT composes will report results to the wiki. > > The event creation logic works exactly as for the 'main' release > stream: relvalconsumer will kick in for every compose that's for the > 'next' Fedora release (so 33 ATM) and decide whether to create an event > depending on how long it's been since the previous event and whether > any 'significant' packages have changed. (I may actually tweak that > 'significant' package list for IoT, now I think about it.) So just as > for the 'main' release stream, we'll get new events every few days, on > average once a week or so. Events can also be manually created if we > particularly want one for a given compose. > > This is a fairly major change to things so there will likely be some > rough edges: please report anything you notice, whether it's straight > up bugs or just things like boilerplate text that doesn't actually > entirely make sense for an alternate release stream, stuff like that. > > It still hasn't been decided (AFAIK) if IoT will be a release-blocking > deliverable/primary Edition for Fedora 33, but this change should set > us up well if it is, and if it isn't, we can just treat this whole > stream as 'optional extra' testing, it still won't hurt to have the > events. > > Thanks folks! > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > > _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
