Update Direction on WNP update launch from Mozilla.org to Firefox.com
Categories
(Release Engineering :: Release Automation, task)
Tracking
(firefox152 fixed)
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: sherrera, Assigned: jlorenzo)
References
Details
Attachments
(6 files, 2 obsolete files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
53 bytes,
text/x-github-pull-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
Currently when Firefox is updated the browser directs to mozilla.org. We need this direction to update to https://www.firefox.com/{locale}/whatsnew/{version}/.
Comment 1•6 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•6 months ago
|
||
:mpohle, can you verify whether this belongs to Toolkit :: Application Update? The actual URL changes needed are in browser/config/whats_new_page.yml (fed to Balrog via Taskcluster) and browser/branding/nightly/pref/firefox-branding.js, which seem more in scope for Release Engineering or Firefox Desktop.
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 3•6 months ago
|
||
| Assignee | ||
Comment 4•6 months ago
|
||
| Assignee | ||
Comment 5•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
Comment 6•6 months ago
|
||
| Assignee | ||
Comment 7•6 months ago
|
||
| Assignee | ||
Comment 8•6 months ago
|
||
| Assignee | ||
Comment 9•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 10•6 months ago
|
||
Comment on attachment 9559159 [details]
Bug 2025987 - part 5: AGENTS.md: document Differential Revision footer behavior r=#ai4dev-reviewers
Revision D290386 was moved to bug 2026927. Setting attachment 9559159 [details] to obsolete.
Comment 11•5 months ago
|
||
Comment 12•5 months ago
|
||
Comment 13•5 months ago
•
|
||
Backed out for causing bc failures @browser_releaseNotesURL.js.
- Backout link
- Push with failures
- Failure Log @browser_releaseNotesURL.js.
- Failure Log
Comment 15•5 months ago
|
||
Comment 16•5 months ago
|
||
Comment 17•5 months ago
|
||
Backed out for causing mochitest failures @RemoteWebNavigation.sys.mjs
- Backout link - recommended without hyperlink
- Push with failures
- Push with failures
- Failure Log BC2
- Failure Log BC10
| Assignee | ||
Comment 18•5 months ago
|
||
The test bug causing the failure is fixed.
I've done some extensive testing to try to find any potential additional regression. I create a try-push with my changes and another without. There are more than 300 failed tasks on both. I also used tests.firefox.dev to see if there's any pattern I missed. I don't see anything that I interpret as a direct regression caused by this stack of patches. I'm attempting another landing.
Comment 19•5 months ago
|
||
Comment 20•5 months ago
|
||
Comment 21•5 months ago
|
||
Backed out for causing bc failures at RemoteWebNavigation
Backout Link
Push with failures tier1
Push with failure tier2
Failure Log
Failure line Hit MOZ_CRASH(Attempting to connect to non-local address! opener is [resource://gre/modules/RemoteWebNavigation.sys.mjs:174:35], uri is [https://www.firefox.com/en-US/whatsnew/]) at checkouts/gecko/netwerk/protocol/http/nsHttpChannel.cpp:X
| Assignee | ||
Comment 22•5 months ago
|
||
I have a fix for this test failure:
startup.homepage_override_url_nimbus='https://www.firefox.com/en-US/whatsnew/|...'
RemoteAgent TRACE: Document already finished loading: https://www.firefox.com/en-US/whatsnew/
TEST-PASS | browser_whats_new_page_nimbus.js | took 538ms
TEST-PASS | browser_whats_new_page_nimbus_disable.js | took 599ms
I ran an extensive try-push to identify any other failure. There was a lot of noise. I compared it to a try-push without my changes which had the same amount of noise. tests.firefox.dev didn't highlight any errors with firefox.com or wnp again. I'm attempting another landing.
Comment 23•5 months ago
|
||
Comment 24•5 months ago
|
||
| bugherder | ||
| Assignee | ||
Comment 25•4 months ago
|
||
| Assignee | ||
Comment 26•4 months ago
|
||
Reopening. Per Steve Jalim, the new WNP URL should only contain the major version number.
| Assignee | ||
Updated•4 months ago
|
Updated•4 months ago
|
Comment 27•4 months ago
|
||
Comment 28•4 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•4 months ago
|
Description
•