Confirmed users
4,293
edits
Software Update:Nightly update infrastructure: Difference between revisions
Software Update:Nightly update infrastructure (view source)
Revision as of 18:08, 11 May 2006
, 11 May 2006no edit summary
mNo edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=Tinderbox= | =Tinderbox= | ||
The tinderbox produces the nightly build & | The tinderbox produces the nightly build & mar file for a complete update, and publishes them to the FTP. It also creates a complete-update snippet, which describes the update, and copies that to AUS. | ||
==mozconfig== | ==mozconfig== | ||
| Line 17: | Line 17: | ||
To pull the code for complete update generation you need: | To pull the code for complete update generation you need: | ||
mk_add_options MOZ_CO_MODULE="mozilla/tools/update-packaging" | mk_add_options MOZ_CO_MODULE="mozilla/tools/update-packaging" | ||
This line is also used | |||
ac_add_options --enable-update-packaging | ac_add_options --enable-update-packaging | ||
The mar executable is built by default. | but it's not obvious why, because mbsdiff (the binary diff executable) is not required for a complete update, only mozilla/tools/update-packaging/{make_full_update.sh,common.sh}. | ||
The mar executable (mozilla/modules/libmar) is built by default. | |||
==Snippet configuration== | ==Snippet configuration== | ||
| Line 34: | Line 37: | ||
| $update_product || "Firefox" || Product identifier for AUS | | $update_product || "Firefox" || Product identifier for AUS | ||
|- | |- | ||
| $update_version || " | | $update_version || "2.0" || "Branch" identifier for AUS | ||
|- | |- | ||
| $update_platform || "WINNT_x86-msvc" || Platform ABI for AUS | | $update_platform || "WINNT_x86-msvc" || Platform ABI for AUS | ||
| Line 42: | Line 45: | ||
| $update_filehost || "mozilla.osuosl.org" || The server that provides the mar files | | $update_filehost || "mozilla.osuosl.org" || The server that provides the mar files | ||
|- | |- | ||
| $update_appv || " | | $update_appv || "2.0a2" || Version that appears in the update notification dialog | ||
|- | |- | ||
| $update_extv || " | | $update_extv || "2.0a2" || Version used to check extension compatibility (this seems to not work properly all the time) | ||
|} | |} | ||
The examples reflect current real world values (**CHECK**) rather than the older values in tinder-defaults.pl. | |||
The snippet is scp'ed to | The snippet is scp'ed to | ||
| Line 128: | Line 133: | ||
'3.0a1'=>'trunk' | '3.0a1'=>'trunk' | ||
So there is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 needs fixing up ([https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497] made a bit of a mess), an $update_version of "1.5.x.y" would be more appropriate. | So there is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 branch needs fixing up ([https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497] made a bit of a mess), an $update_version of "1.5.x.y" would be more appropriate. | ||