Adam Williamson 35735f21cd Pungi 4 conversion: handle Pungi-derived BUILD and FLAVOR ... With the arrival of Pungi 4, the scheduler is no longer using fedfind-provided BUILD and FLAVOR values, but ones derived from Pungi properties. BUILD is now simply the Pungi compose_id. FLAVOR is produced by joining the Pungi variant, type, and format with '-' characters as the separators. Pungi, unfortunately, does not treat 'Rawhide' as a release, it synthesizes a release number for Rawhide composes and places that in the compose ID. To cope with that, for now, the scheduler will set RAWHIDE to '1' if the compose is a Rawhide one. As we have to adapt all places where we parse the release in any case, this commit consolidates them into a fedorabase subroutine. For the one place where we also used to parse the 'milestone' from fedfind, there is a placeholder get_milestone subroutine which currently returns an empty string, as I don't yet have a good handle on how to draw the kinds of distinctions fedfind mapped to 'milestone' from Pungi metadata.		2016-02-23 11:08:45 -08:00
..
anacondatest.pm	anaconda.core dumps have PID suffix, so correct for that	2015-12-14 08:29:19 -08:00
fedorabase.pm	Pungi 4 conversion: handle Pungi-derived BUILD and FLAVOR	2016-02-23 11:08:45 -08:00
fedoradistribution.pm	fix some warnings that are shown during test loading	2016-02-10 09:42:56 +01:00
installedtest.pm	use validate_script_output instead of typing and needles matching	2015-11-04 14:38:36 +01:00