branches: add esr branch support (bug 2048638)#2198
Open
Magnolia-Liu wants to merge 25 commits into
Open
Conversation
3 similar comments
3 similar comments
Magnolia-Liu
marked this pull request as ready for review
July 14, 2026 15:21
zzzeid
requested changes
Jul 14, 2026
zzzeid
requested changes
Jul 17, 2026
comm-central uses nightly path, not taskcluster.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change makes the CLI + GUI recognize the mozilla-esr / comm-esr / esr pattern and construct the hg repo URL dynamically.
Resolution is a blind HTTP fetch: we build the URL from whatever version the user passes and request it. If that ESR exists on hg the fetch is a hit and bisection proceeds. If it doesn't, the request simply misses and the branch is treated as unavailable.
Previously, mozregression was not working as expected since it could not find any builds when using commands like
mozregression --app thunderbird --repo comm-releasefor Thunderbird branches other than comm-central. This was because comm-esr, comm-release, and comm-beta don't have opt builds, they only have shippable ones.Fix the behaviour for fetching integration builds both for comm-esr branches and other comm branches by implementing similar behaviour as existing tk_routes construction in Firefox.
Add small help text that shows how to fetch ESR branches as they will not show up in the drop down menu.
New UI:
