Closed Bug 1136330 Opened 9 years ago Closed 2 years ago

replacement for releasetest vs. release snippet comparison

Categories

(Release Engineering :: Release Automation: Updates, defect, P5)

Product:
Release Engineering
Component:
Release Automation: Updates
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

Today we hit an issue where users on 24 esr and earlier where being served 34.4.0 instead of 34.5.0 on the "esr" channel. The "esr-cdntest" channel didn't exhibit this behaviour. In the past, we would've caught this with the snippet comparison test that makes sure the live and test channel are exactly the same. Because of the nature of how Balrog works, this test simply doesn't work there.

It would be very good to have some sort of replacement that ensures that what we're testing on the cdntest channel matches what will end up being live. I don't have any ideas off the top of my head for how to do this with rules, unfortunately.
Priority: -- → P5
Component: Release Automation: Other → Release Automation: Updates

snippets are long dead!

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.