Closed Bug 683427 Opened 13 years ago Closed 13 years ago

Can't add new Camino versions to Socorro via Branch Data Sources

Categories

(Socorro :: General, task)

x86
macOS
task
Not set
major

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: alqahira, Unassigned)

References

()

Details

It seems like in the last few weeks I've lost the ability to add new Camino versions to the Branch Data Sources (it worked at the beginning of the month for 2.1b1 and 2.1b2pre). We're releasing 2.0.8 and 2.1b2 in conjunction with the upcoming security releases, so I need to be able to add those versions (and 2.0.9pre and 2.1b3pre) to the branch data sources to be able to generate reports.
This looks like a dupe of bug 679836, but as I'm not 100% sure when that lands, you might want to convert this bug into one to manually add those versions to the DB, which is the best temporary measure until the admin UI fix is being pushed.
Component: Socorro → General
Product: Webtools → Socorro
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #1) > This looks like a dupe of bug 679836, but as I'm not 100% sure when that > lands, you might want to convert this bug into one to manually add those > versions to the DB, which is the best temporary measure until the admin UI > fix is being pushed. Bug 679836 looks like it's been fixed, but I (again) can't add Camino versions from the "Missing Entries" table in Branch Data Sources (it worked fine for the last release).
I should add, trying to "add" brings up the UI, but pressing the "Add Product Version" has crash-stats telling me: Error Something bad happened. It's not you, it's me. Please file an issue in Bugzilla describing what happened, and please include the URL for this page.
Closing as resolved won't fix due to https://bugzilla.mozilla.org/show_bug.cgi?id=733559
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Target Milestone: --- → 2.5.1
Where in the world does one file this new "add version foo" bug so that people will actually respond to it (at least without me having to allot additional time to figure out who to track down to poke)? Bug 731738's gone unloved so long that I now have additional new versions that need adding. (Also, I thought the whole point of the Admin UI when it was added was to let responsible people have the ability to self-serve new versions, rather than having to go through the slow process of getting the Socorro team to run a bunch of SQL every time a project released a new version. And now we're going back to that system!?)
For all other products than Camino, i.e. everything built by the buildbot release automation Firefox, Thunderbird, and SeaMonkey are running, we are automatically adding versions through FTP scraping now, so the admin UI adding was obsoleted. It might even be completely removed in the future.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #6) > release automation Firefox, Thunderbird, and SeaMonkey are running, we are > automatically adding versions through FTP scraping now, so the admin UI Really? The "Missing Entries" table seems to have a lot of seemingly-valid Firefox, Thunderbird, and SeaMonkey versions listed, some with lots and lots of reports (which is why I couldn't believe "add" wasn't working right). Can you point me to a bug/spec that describes how the FTP scraping works? Since it's FTP-scraping being used rather than something that's part of buildbot automation, it seems like we could make it work for Camino, too. (Although, as I said above, this scraping seems not to be working, period, given all the versions of Fx, Tb, and Sm showing up in the "Missing Entries" table.)
(In reply to Smokey Ardisson (not following bugs - do not email) from comment #7) > (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #6) > > > release automation Firefox, Thunderbird, and SeaMonkey are running, we are > > automatically adding versions through FTP scraping now, so the admin UI > > Really? The "Missing Entries" table seems to have a lot of seemingly-valid > Firefox, Thunderbird, and SeaMonkey versions listed, some with lots and lots > of reports (which is why I couldn't believe "add" wasn't working right). Those are erroneously there because the whole mechanism for finding "Missing Entries" is not working correctly any more, as we moved everything to the new mechanisms based on channels and FTP scraping. > Can you point me to a bug/spec that describes how the FTP scraping works? > Since it's FTP-scraping being used rather than something that's part of > buildbot automation, it seems like we could make it work for Camino, too. Possibly you could, but the FTP scraping solution is temporary, we want to get data directly from the build systems in the future, possibly through pulse. > (Although, as I said above, this scraping seems not to be working, period, > given all the versions of Fx, Tb, and Sm showing up in the "Missing Entries" > table.) The scraping is working fine, but the new systems used for builds since the channel model are incompatible with the old stuff where we manually added versions and the "Missing Entries" code only knows about the old stuff - which btw. is deprecated and slated for removal at some point in the future.
Verified wontfix - see comment 8 for details. :kairo, thank you for the excellent explanation.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.