UpdateGeneration: Difference between revisions
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) mNo edit summary |
ChrisCooper (talk | contribs) |
||
| Line 11: | Line 11: | ||
* nightly builders generate complete MAR using Makefile | * nightly builders generate complete MAR using Makefile | ||
* upload complete MAR to staging along with build | * upload complete MAR to staging along with build | ||
* upload snippet to | * upload complete snippet to AUS2 server | ||
* prometheus-vm runs cron script every 5 minutes (patch-packager-cron.sh) that calls patch-packager.pl | * prometheus-vm runs cron script every 5 minutes (patch-packager-cron.sh) that calls patch-packager.pl. In the simplest terms, this script does the following: | ||
*# Read in all of the available builds. | |||
*# Compute all of the patches we could offer. | |||
*# Read in all of the offered patches. | |||
*# Compute which patches we aren't offering which we could. | |||
*# Create all of the patches we could offer. | |||
*# Upload them. | |||
=== Updates for security releases === | === Updates for security releases === | ||
Revision as of 23:53, 14 July 2009
Update generation
One of the key features of Firefox is the update system that allows Mozilla to push out bug fixes and new features to users automatically.
Current processes
Currently we use two different sets of processes and tools to generate updates for nightly updates and releases.
Nightly updates
- nightly builders generate complete MAR using Makefile
- upload complete MAR to staging along with build
- upload complete snippet to AUS2 server
- prometheus-vm runs cron script every 5 minutes (patch-packager-cron.sh) that calls patch-packager.pl. In the simplest terms, this script does the following:
- Read in all of the available builds.
- Compute all of the patches we could offer.
- Read in all of the offered patches.
- Compute which patches we aren't offering which we could.
- Create all of the patches we could offer.
- Upload them.