We want to get more users to test our nightly builds. The main hurdle currently is the missing auto-update. This is the parent ticket that tracks this task.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
generating new certificates to sign the nightly mars, and adding them in tor-browser in toolkit/mozapps/update/updater/Makefile.in (for the public part), and on the nightly build machine
changing the version number (currently set to 'tbb-nightly') to an increasing version number (maybe the date ?), so that the updater can see it as a new version
updating the nightly build scripts to sign the mar files, generate the xml update responses and upload them somewhere
While working on #26045 (moved) we realized that for nightly builds as they are produced today it is not sufficient to just replace the nightly_aurora_level3* certificates Mozilla uses for such cases. The reason for that is that our update channel is default which lets the code use the dep1.der and dep2.der certificates instead.
I guess it is not unreasonable to move to a nightly update channel and then only replace the nightly_aurora_level3* certs.