Closed Bug 1486035 Opened 4 years ago Closed 4 years ago
figure out a better fix for aurora versions
A while back, to fix bug #1418037, we wrote up an AuroraVersionFixitRule. I think when I worked through that bug and wrote up that rule, I didn't really understand the specifics of what was going on and why. That rule does alleviate the issue, but it requires us to update the builds every time a new version comes out. It's kind of annoying. The theory in the comments of that bug is that a real fix involves fixing ftpscraper or the stored procedure for adding new versions or something involved like that. This bug covers revisiting all of that, getting the specifics, and then figuring out a better fix.
I'd be good to fix this for reals. It reduces the need to keep track of the release schedule and when the build we need to fix comes out and then fixing it in a timely manner and reprocessing. Making this a P2.
Priority: -- → P2
I'm pretty sure we can nix this if we rewrite BetaVersionRule to use Buildhub.
Depends on: 1501780
I just rewrote the BetaVersionRule to use Buildhub. That was fixed in: https://github.com/mozilla-services/socorro/pull/4658 That landed just now. Given that it nixes the AuroraVersionFixitRule, I'm going to mark this bug FIXED, too.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.