We're going to be hosting full windows installers for some partners, which a custom stub then downloads, so we need some -latest bouncer products. We can already create products in the form Firefox-<version>-<partner> for non-ssl downloads.
This work adds a new alias of the form partner-firefox-<branch>-<partner>-latest. The partner- prefix was selected to visually and logically separate out those aliases from non-partner. One change from our current scheme is giving <branch> a value for release (instead of leaving it off) to avoid any ambiguity in the regular expression matching.
This also adds stub support, same as above but with a -stub suffix instead of -latest; and checking bouncer stage in staging releases.
We're going to be hosting full windows installers for some partners, which a custom stub then downloads, so we need some
-latest
bouncer products. We can already create products in the formFirefox-<version>-<partner>
for non-ssl downloads.This work adds a new alias of the form
partner-firefox-<branch>-<partner>-latest
. Thepartner-
prefix was selected to visually and logically separate out those aliases from non-partner. One change from our current scheme is giving<branch>
a value for release (instead of leaving it off) to avoid any ambiguity in the regular expression matching.This also adds stub support, same as above but with a
-stub
suffix instead of-latest
; and checking bouncer stage in staging releases.