Closed Bug 1314448 Opened 8 years ago Closed 6 years ago

Create a build target that adds --disable-webrtc to the mozconfig

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: tjr, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tor][tor-testing][fingerprinting]) 

To proactively detect breakage (such as #1304490) that will affect Tor Browser, we would like to add a build target (perhaps a platform?) that will add the --disable-webrtc mozconfig option and then compile and confirm the compilation occurs successfully.
Component: Tools → General Automation
QA Contact: hwine → catlee
Whiteboard: [tor-testing] → [tor][tor-testing][fingerprinting]
Priority: -- → P1
On which platforms?
(In reply to Chris AtLee [:catlee] from comment #1)
> On which platforms?

linux, linux64, macosx, win32, win64 (to be future-proof this isn't needed right now), and Android.
Whiteboard: [tor][tor-testing][fingerprinting] → [tor][tor-testing][fingerprinting][fp:m1]
Priority: P1 → P2
Whiteboard: [tor][tor-testing][fingerprinting][fp:m1] → [tor][tor-testing][fingerprinting]
Priority: P2 → P3
Whiteboard: [tor][tor-testing][fingerprinting] → [tor][tor-testing][fingerprinting][fp-triaged]
Component: General Automation → General
Whiteboard: [tor][tor-testing][fingerprinting][fp-triaged] → [tor][tor-testing][fingerprinting]
MinGW builds use --disable-webrtc
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.